team-combat

**Argument check:** If no combat feature description is provided, output: > "Usage: `/team-combat [combat feature description]` — Provide a description of the combat feature to design and implement (e.g., `melee parry system`, `ranged weapon spread`)." Then stop immediately without spawning any subagents or reading any files. When this skill is invoked with a valid argument, orchestrate the combat team through a structured pipeline. **Decision Points:** At each phase transition, use `AskUserQuestion` 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 - **game-designer** — Design the mechanic, define formulas and edge cases - **gameplay-programmer** — Implement the core gameplay code - **ai-programmer** — Implement NPC/enemy AI behavior for the feature - **technical-artist** — Create VFX, shader effects, and visual feedback - **sound-designer** — Define audio events, impact sounds, and ambient combat audio - **engine specialist** (primary) — Validate architecture and implementation patterns are idiomatic for the engine (read from `.claude/docs/technical-preferences.md` Engine Specialists section) - **qa-tester** — Write test cases and validate the implementation ## How to Delegate Use the Task tool to spawn each team member as a subagent: - `subagent_type: game-designer` — Design th...