test-environments
Installation
SKILL.md
Discovery Questions
Check .agents/qa-project-context.md first — if it exists, use it and skip anything already
answered there. Then:
- How many environments exist today? Local dev, CI, staging, preview, production? Map what you have before designing what you need.
- Is the app containerized? Check for
Dockerfile,docker-compose.yml, orcompose.yaml. If yes, multi-stage targets and compose come for free; if not, that is the first deliverable. - How is test data seeded? Manual SQL, migration-based, factory libraries, or production snapshots? This decides whether seed scripts are a quick win or a rewrite.
- How close is staging to production? Same DB engine, queue, cache, auth provider, orchestration? Each mismatch is a class of bugs staging can never catch.
- External dependencies: How many third-party APIs does the system call, and are they stubbed in non-prod? Unstubbed third parties are the top source of CI flake.