claude▌

### Test Flakiness - description: "Detect non-deterministic (flaky) tests by reading CI run logs or test result history. Aggregates pass rates per test, identifies intermittent failures, recommends quarantine or fix, and - argument-hint: "[ci-log-path | scan | registry]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash

### Team Qa - description: "Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a - argument-hint: "[sprint | feature: system-name]" - allowed-tools: Read, Glob, Grep, Write, Task, AskUserQuestion

### Gate Check - description: "Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to - argument-hint: "[target-phase: systems-design | technical-setup | pre-production | production | polish | release] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Bash, Write, Task, AskUserQuestion

### Launch Checklist - name: launch-checklist - description: "Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs." - argument-hint: "[launch-date or 'dry-run']"

### Soak Test - description: "Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that - argument-hint: "[duration: 30m | 1h | 2h | 4h] [focus: memory | stability | balance | all]" - allowed-tools: Read, Glob, Grep, Write

### Reverse Document - name: reverse-document - description: "Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs." - argument-hint: "<type> <path> (e.g., 'design src/gameplay/combat' or 'architecture src/core')"

### Design System - description: "Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, - argument-hint: "<system-name> [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion, TodoWrite

### Playtest Report - name: playtest-report - description: "Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis." - argument-hint: "[new|analyze path-to-notes] [--review full|lean|solo]"

### Propagate Design Change - name: propagate-design-change - description: "When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user - argument-hint: "[path/to/changed-gdd.md]"

### Onboard - description: "Generates a contextual onboarding document for a new contributor or agent joining the project. Summarizes project state, architecture, conventions, and current priorities relevant to the - argument-hint: "[role|area]" - allowed-tools: Read, Glob, Grep, Write