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.

Phase 0: Resolve Review Mode

1. If --review [mode] was passed as an argument, use that mode.
2. Else read production/review-mode.txt — use whatever is written there.
3. Else default to lean.