qa-plan

# QA Plan This skill generates a structured QA plan for a sprint, feature, or individual story. It reads all in-scope story files and their referenced GDDs, classifies each story by test type, and produces a plan that tells developers exactly what to automate, what to verify manually, what the smoke test scope is, and when to bring in a playtester. Run this before a sprint begins so the team knows upfront what testing work is required. A test plan written after implementation is a post-mortem, not a plan. **Output:** `production/qa/qa-plan-[sprint-slug]-[date].md` --- ## Phase 1: Parse Scope **Argument:** `$ARGUMENTS` (blank = ask user via question) Determine scope from the argument: - **`sprint`** — read the most recent file in `production/sprints/`, extract every story file path referenced. If `production/sprint-status.yaml` exists, use it as the primary story list and fall back to the sprint plan for story metadata. - **`feature: [system-name]`** — glob `production/epics/*/story-*.md`, filter to stories whose file path or title contains the system name. Also check the epic index file (`EPIC.md`) in that system's directory. - **`story: [path]`** — validate that the path exists and load that single file. - **No argument** — use `question`: - "What is the scope for this QA plan?" - Options: "Current sprint", "Specific feature (enter system name)", "Specific story (enter path)", "Full epic" After resolving scope, report: "Building QA plan for [N] sto...