What problem does it solve?
This Skill removes the guesswork from planning quality assurance by turning sprint, feature, or story artifacts into a clear test strategy before implementation begins.
Core Features & Use Cases
- Story Classification: Reads story files and classifies them into the right test type so teams know whether they need contract, smoke, migration, permission, workflow, UI, integration, deployment, or config checks.
- Evidence-Oriented Planning: Produces concrete automated and manual verification guidance, including smoke scope, required evidence, and sign-off expectations.
- Repository-Aware QA: Uses CDDs, ADRs, sprint plans, and related docs to ground the test plan in the actual project context.
- Use Case: A QA lead preparing for a new sprint can generate a structured plan that tells developers exactly what to test, what artifacts to create, and what must be approved before stories are marked complete.
Quick Start
Ask the assistant to generate a QA plan for the current sprint, a specific feature, or a single story from the repository.