What problem does it solve?
QA planning usually happens after implementation, which creates rework and missed regressions because the team only learns what to test once changes are already done.
Core Features & Use Cases
- Sprint/feature/story scope resolution: Builds a plan from the current sprint, a specific feature/system, a single story path, or an entire epic.
- Requirement-driven test classification: Reads story files and referenced GDD sections (Acceptance Criteria, Formulas, Edge Cases) to classify tests as Logic, Integration, Visual/Feel, UI, or Config/Data.
- Actionable outputs for automation and hand-off: Produces automated-test requirements, manual verification steps, smoke test scope, and playtest sign-off rules, and writes the result to a dated file.
Quick Start
Run qa-plan for the current sprint so the team receives a structured QA plan covering automated tests, manual checks, smoke scope, and playtest requirements.