What problem does it solve?
This skill generates a structured QA plan for a sprint, feature, or individual story by reading all in-scope story files and their referenced GDDs, classifying each story by test type, and producing a plan that tells developers exactly what testing work is required, including automated tests, manual verifications, smoke-test scope, and playtest sign-off requirements. Run before a sprint begins so the team knows upfront what testing work is required.
Core Features & Use Cases
- Scope resolution: resolve sprint/feature/story scope using arguments or AskUserQuestion
- Input loading: read stories and GDD/ADR references to extract acceptance criteria, estimates, and dependencies
- Classification: assign a test type to each story
- Output generation: produce a QA plan at production/qa/qa-plan-[sprint-slug]-[date].md
- Gap handling: note missing files without failing the plan
Quick Start
Run qa-plan with a scope argument to generate a plan for a sprint, feature, or individual story.