qa-planlisted

# `/qa-plan` — QA Strategy and Classification Analyze changes or a feature and produce a classified QA plan. Works standalone or as the verification phase of an autonomous development pipeline. ## Usage ``` /qa-plan # Analyze uncommitted changes (PR mode) /qa-plan <branch> # Analyze branch diff against default branch (PR mode) /qa-plan @<handoff-path> # Analyze with handoff QA Expectations cross-check (PR mode) /qa-plan <freeform description> # Feature-scoped QA from docs, specs, code exploration ``` ## Process ### Step 1: Gather Context Determine the **scope mode** from the arguments: #### Mode A: PR / Diff Scope (default when no freeform description) 1. **Get the diff** — `git diff` (uncommitted) or `git diff <default-branch>...<branch>` (branch) 2. **Identify changed files** — group by type (models, controllers, views, services, config, tests) 3. **Read handoff QA Expectations** — if handoff path provided or discoverable, extract expected verification scenarios #### Mode B: Feature / Freeform Scope When the user provides a freeform description, references docs/specs, or the scope clearly exceeds a single PR: 1. **Read provided documents** — PDFs, specs, handoffs, UAT plans, or any referenced files 2. **Explore the codebase** — use an Explore agent to map the feature surface area: - UI components, pages, and routes involved - Controllers and API endpoints - Models, state machines, and callbacks - Bac