What problem does it solve? Teams often start a sprint without knowing what testing work is required, leading to untested features and post-mortem test plans. This Skill reads story files and GDDs upfront and produces a concrete QA plan covering automated tests, manual checks, smoke scope, and playtest sign-offs. ## Core Features & Use Cases - Story Classification: Classifies each story as Logic, Integration, Visual/Feel, UI, or Config/Data based on acceptance criteria, respecting any declared Type field. - Test Plan Generation: Produces a structured plan with automated test specs (file paths, formulas, edge cases), manual QA checklists, smoke test scope, and playtest requirements. - Story Back-filling: Optionally writes test case specs back into each story file's QA Test Cases section for traceability with dev-story and code-review workflows. - Use Case: Before a sprint begins, run the skill against the current sprint to get a complete QA plan telling developers exactly which unit and integration tests to write and which stories need playtester sign-off. ## Quick Start Ask the AI to generate a QA plan for the current sprint using the qa-plan skill and write it to the production/qa directory.
