What problem does it solve?
It prevents brittle, last-minute testing by turning sprint/feature scope (stories plus referenced GDD acceptance criteria) into a complete, actionable QA plan that developers and QA can execute immediately.
Core Features & Use Cases
- Sprint/feature/story scope intake: Accepts
sprint, feature: system-name, story: path, or prompts for scope when omitted, then enumerates in-scope story files.
- Spec-driven test classification: Reads each story’s acceptance criteria and classifies it into Logic, Integration, Visual/Feel, UI, or Config/Data with a conservative bias toward Integration when ambiguous.
- Automated + manual QA coverage: Produces a structured plan including automated test requirements (unit/integration paths), manual verification checklists, smoke-test scope, and playtest sign-off requirements.
- GDD acceptance-criteria targeting: Loads only the GDD Acceptance Criteria and Formulas sections for each referenced GDD, minimizing noise while ensuring tests track real requirements.
- Gap detection: Notes missing GDD references without blocking plan generation so the team can address specification coverage gaps.
Quick Start
Ask for a QA plan by running the qa-plan skill with the argument sprint to generate a production QA plan file for the current sprint’s stories.