SKILL.md
Team Combat
Argument check: If no combat feature description is provided, output:
"Usage:
/team-combat [combat feature description] [--review full|lean|solo]— 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.
In collaborative mode, the user must approve before moving to the next phase.
In guided mode the pipeline advances automatically unless a phase is BLOCKED;
in autonomous mode it runs end to end, recording each phase outcome via
log_decision. Decisions in automation_always_ask categories
(is_always_ask_category helper) always prompt regardless of mode. See
.claude/docs/automation-modes.md.