What problem does it solve?
QA planning is often done after work begins, leaving teams unprepared for required automated tests, manual verification steps, and playtest sign-off. This Skill centralizes requirements by reading story files and referenced GDDs to produce a clear, actionable QA plan before development starts, reducing rework and missed test coverage.
Core Features & Use Cases
- Scope parsing: Resolve scope from a sprint, feature, or single story and report missing story files without failing the plan.
- Input extraction: Read story titles, acceptance criteria, implementation files, estimates, dependencies, and referenced GDD formulas and acceptance sections.
- Classification & mapping: Classify stories as Logic, Integration, Visual/Feel, UI, or Config/Data and map each to automated test paths, manual checklists, smoke tests, and playtest requirements.
- Output generation: Assemble a full QA plan Markdown file under production/qa with test summaries, automated test guidance, manual verification checklists, smoke scope, and Definition of Done gates.
- Collaborative protocol: Conservatively classify ambiguous stories, flag missing GDDs, and require explicit user approval before writing the plan file.
Quick Start
Create a QA plan for the current sprint and write it to production/qa by asking: "Generate QA plan for sprint".