team-qa

When this skill is invoked, orchestrate the QA team through a structured testing cycle. **Decision Points:** At each phase transition, use `question` to present the user with the subagent's proposals as selectable options. Write the agent's full analysis in conversation, then capture the decision with concise labels. The user must approve before moving to the next phase. ## Team Composition - **qa-lead** — QA strategy, test plan generation, story classification, sign-off report - **qa-tester** — Test case writing, bug report writing, manual QA documentation ## How to Delegate Use the Task tool to spawn each team member as a subagent: - `subagent_type: qa-lead` — Strategy, planning, classification, sign-off - `subagent_type: qa-tester` — Test case writing and bug report writing Always provide full context in each agent's prompt (story file paths, QA plan path, scope constraints). Launch independent qa-tester tasks in parallel where possible (e.g., multiple stories in Phase 5 can be scaffolded simultaneously). ## Pipeline ### Phase 1: Load Context Before doing anything else, gather the full scope: 1. Detect the current sprint or feature scope from the argument: - If argument is a sprint identifier (e.g., `sprint-03`): read all story files in `production/sprints/[sprint]/` - If argument is `feature: [system-name]`: glob story files tagged for that system - If no argument: read `production/session-state/active.md` and `production/sprint-status.yaml` (if present...