qa-start

Without this launcher, engineers often jump to writing tests before defining what to test or why. This skill prevents that.

When to Use This

• Starting QA on a brand-new project with no existing test infrastructure
• Joining an existing codebase that has no QA setup at all
• Onboarding a QA engineer to a project where quality work has never been formalized
• Rebooting QA after a period of neglect (tests deleted, coverage collapsed, no strategy)
• Any situation where the answer to "where do we start?" is unclear

Step 1: Capture Project Context

Skill: qa-project-context

This step creates .agents/qa-project-context.md in your project root. That file records your tech stack, test frameworks, CI/CD pipeline, environments, coverage goals, risk areas, and team structure. Every subsequent skill reads it to avoid asking you the same questions repeatedly.