qa-plan

Run the qa-plan skill with a sprint, feature, or story argument. It reads the in-scope story files and referenced GDDs, classifies each story by test type, and writes a plan to production/qa/ covering automated tests, manual checks, and smoke test scope.

Stories with a declared Type field in their header are accepted as-is. Otherwise the type is inferred from acceptance criteria: formulas and state transitions indicate Logic, cross-system interactions indicate Integration, animation and feel indicate Visual/Feel, and menus or HUD elements indicate UI.

The plan notes the gap but does not block. Test cases are then derived from acceptance criteria alone, and the plan flags that the GDD Formulas section should be reviewed before writing tests rather than inventing formulas.

Yes. With user approval, the skill writes generated test case specs into each Logic and Integration story's QA Test Cases section, and manual verification steps for Visual/Feel and UI stories, enabling traceability with code review and story completion workflows.

Before the sprint begins or when starting a major feature. A plan written after implementation is a post-mortem; creating it upfront tells developers which test files to create before stories can be marked done.