Team Combat

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.

Phase 0: Resolve Config

!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,team.size,workflow

Resolved above — use as-is; --review overrides review_mode. No block → defaults in .claude/docs/config-resolution.md.

review_mode sets director-gate depth, and this pipeline has no director gate: no phase below spawns CD-, TD-, PR- or AD-PHASE-GATE, at any review_mode. Its phase gates are the pipeline's own decision points (defined under team.size below), and the agents that work at them are team members, not director gates.

automation drives the Decision Points note above. See the Decision Points note above and .claude/docs/automation-modes.md for how each mode changes pipeline behavior.

workflow sizes the Phase 1 design document the way /design-system does: ## Summary plus all 8 sections at full; at standard, Overview, Detailed Design, Edge Cases, Dependencies and Acceptance Criteria, plus Formulas whenever the mechanic defines numeric rules (a combat mechanic almost always does); at minimal the game brief is the design record and the GDD is optional — draft those five sections and tell the user it is optional at this workflow level.