!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow,qa.level,system_overrides

Resolved above, use as-is. No block → defaults in .claude/docs/config-resolution.md.

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

---

Every AskUserQuestion call follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

Workflow tier: resolve per the GDD's system as each is read (per .claude/docs/workflow-modes.md): workflow_overrides.system_overrides.<system> if the block lists one, else the project value. It sets how many GDD sections the test plan is mined from, see Phase 2.

qa.level: at minimal, produce only a minimal smoke plan, drop the automated-test-required rows and the test-file DoD; at standard, a full plan per story type; at full, also add per-system coverage targets. Distinct axis from workflow (which sets how many GDD sections are mined). No level drops the Visual/Feel and UI screenshot rows, tests are waived at minimal, the look is not (.claude/docs/coding-standards.md).

Phase 1: Parse Scope

Argument: $ARGUMENTS (blank = ask user via AskUserQuestion)

Determine scope from the argument: