What problem does it solve?
Projects often skip creating a formal test strategy until after implementation, leaving developers without clear guidance on what to automate, what must be verified manually, and how to gate release readiness. This Skill ensures QA work is planned before development begins by turning story files and referenced GDDs into an actionable test plan.
Core Features & Use Cases
- Scope resolution: Determine scope from a sprint, a named feature, or a single story and handle missing referenced files without failing the plan.
- Automated extraction: Read story acceptance criteria and referenced GDD Formulas to derive testable requirements and file lists.
- Classification & output: Classify stories into Logic, Integration, Visual/Feel, UI, or Config/Data, produce automated test paths, manual checklists, smoke test scope, and playtest sign-off rules.
- Collaborative guardrails: Conservative classification rules, explicit AskUserQuestion fallback for scope, and a required user confirmation step before writing the plan to production.
Quick Start
Create a QA plan for the current sprint that lists automated tests, manual checklists, smoke test scope, and playtest requirements.