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.

team.size: which agents are active (orthogonal to review_mode gate-depth and workflow docs).

• individual (default): gameplay-programmer runs the pipeline; escalate ai-programmer only if the feature flags AI work. Other Team Composition agents are consulted via the gameplay-programmer, not spawned separately.
• small: the full Team Composition pipeline below, as documented.
• studio: full pipeline + engine sub-specialists + an adversarial review pass. Engine sub-specialists: the primary engine specialist's prompt says it may hand parts of its review to the sub-specialists its tools: grant names (for example ue-gas-specialist for abilities); below studio it answers alone. Adversarial review pass: Phase 5's qa-tester is told "your job is not to confirm this works — find how it breaks", and the report says the pass ran. A non-core agent needed at individual routes through the nearest active core agent with an informational note. "Phase gate" means any phase that ends in an AskUserQuestion decision point this pipeline itself lists — a transition under Decision Points above, or a Gate step written into the pipeline below — whatever the automation mode. guided and autonomous change how a gate is passed (it auto-advances, or is recorded with log_decision), not whether it is one, so bounded-exception condition (3) below holds at it in every mode. An agent restricted to "phase gates only" is spawned at those points and no others. This active-set scoping applies throughout the pipeline below: any phase that names an agent outside the active set routes through the nearest core agent rather than spawning it.

Announce the active set before Phase 1 — never let the collapse be silent. Before spawning anything, state in one line which agents this run will actually spawn, and which the pipeline below names but will not spawn at the resolved team.size. For example:

Active set (team.size: <resolved>): <the agents listed for that size above>. Not spawned this run: <every other agent this pipeline names> — consulted through <nearest active core agent>. Raise team.size (or modes.rigor) to widen.

Fill it from the team.size list directly above and the agents this file's own pipeline names — not from an example. Both sets differ per orchestrator.

The pipeline below reads as a multi-agent fan-out and at the shipped default it is one or two agents — team-release names ten and runs one, team-narrative names six across five phases and runs writer alone. The collapse is correct: team.size is rigor-fronted and the narrow default is the token lever. Without saying so, a reader cannot distinguish a correctly-collapsed run from a broken pipeline, and the per-agent "routes through the nearest core agent with an informational note" rule above fires at routing time and never states the shape of the run as a whole.

This is the same rule as the skipped-check reporting elsewhere in this file: a constraint that is enforced but never surfaced is indistinguishable, to the person reading the output, from one that was never enforced.

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 (the primary specialist is <engine>-specialist from engine.name — Godot→godot-specialist, Unity→unity-specialist, Unreal→unreal-specialist; fall back to the Primary line of ## Engine Specialists in technical-preferences.md)
• qa-tester — Write test cases and validate the implementation

How to Delegate

Use the Agent tool to spawn each team member as a subagent:

• subagent_type: game-designer — Design the mechanic, define formulas and edge cases
• subagent_type: gameplay-programmer — Implement the core gameplay code
• subagent_type: ai-programmer — Implement NPC/enemy AI behavior
• subagent_type: technical-artist — Create VFX, shader effects, visual feedback
• subagent_type: sound-designer — Define audio events, impact sounds, ambient audio
• subagent_type: [primary engine specialist] — Engine idiom validation for architecture and implementation
• subagent_type: qa-tester — Write test cases and validate implementation

Brief each agent — do not dump context. Read the shared inputs once and pass a distilled brief inline: the lines each agent actually needs, never a file path for a document you have already read (an agent handed a path re-reads the whole file). Pass a path only for a document you have not read and only that agent needs.

End every agent prompt with a return contract: "Write your full output to [path] — that named path is your write authorisation under the bounded exception below, so write it without a separate approval prompt. Return only (1) the path written, (2) a ≤5-bullet summary of decisions, (3) any BLOCKED/CONCERNS items, one line each. Do not restate the documents you read." Without it, an agent returns everything it read back into this session. Implementation files are the exception: an agent writing code or assets first returns the files it will create or change, and its return contract names them only after you have asked once for the set and the user said yes (File Write Protocol) — that answer, not the bounded exception, authorises those writes.

Substitute a real path for [path]. Every phase that produces an artifact names one; most are fixed by the skill that already reads them:

Phase / agent	Writes to	Destination fixed by
1 game-designer (draft)	production/combat/[feature]-gdd-draft.md	this skill — you write the final design/gdd/[feature].md (Phase 1)
2 gameplay-programmer	docs/architecture/[feature]-sketch.md	see note below
2 engine specialist	docs/architecture/[feature]-engine-notes.md	see note below
3 gameplay-programmer, ai-programmer, technical-artist	the code root and assets/ — the files the Phase 3 approval lists	outside the bounded exception: asked once for the set (File Write Protocol)
3 sound-designer	production/combat/[feature]-audio-events.md	this skill
5 qa-tester (test cases)	production/qa/test-cases/[feature]-cases.md	/team-qa Phase 4
5 qa-tester (bugs)	production/qa/bugs/BUG-[NNNN].md	/team-qa Phase 5

Phase 6 is a spoken status report, not an artifact — no path, and none needed.

Every phase above names a concrete destination, deliberately. The Error Recovery Protocol below says "a named artifact that is not on disk is a failed phase" — a check that cannot run when no path was named.

The two docs/architecture/ entries are a judgement call, not a convention. That directory holds ADRs (adr-NNNN-*.md); a sketch is a precursor to one, not one itself, and nothing in the repo reads either file. Say so when reporting, so the sketch is understood as a record rather than an input to a later gate.

Why this does not violate the Collaboration Protocol. CLAUDE.md requires an agent to ask "May I write this to [filepath]?" before Write/Edit. A subagent spawned here writes without asking, and that is a deliberate, bounded exception rather than an oversight — the same call already made for consistency-check appending to active.md. The exception holds only when all three are true: (1) the path is one you named in the prompt, so the user approved the destination when they approved the phase; (2) it is a new artifact under production/, docs/ or tests/, never an edit to existing source or config; (3) the phase that produced it is itself gated by an AskUserQuestion before the pipeline advances. Outside those three, the agent must ask. Do not "fix" this by asking per subagent — a prompt per agent per phase makes an orchestrator unusable, which is why the exception exists.

Launch independent agents in parallel where the pipeline allows it (e.g., Phase 3 agents can run simultaneously).

Pipeline

Phase 1: Design

Delegate to game-designer:

• Create or update the design document for design/gdd/[feature].md from .claude/docs/templates/game-design-document.md, with ## Summary and the sections workflow requires (Phase 0) — at full: mechanic overview, player fantasy, detailed rules, formulas with variable definitions, edge cases, dependencies, tuning knobs with safe ranges, and acceptance criteria
• Output: completed design document, drafted to production/combat/[feature]-gdd-draft.md

design/ is outside the bounded write exception above, so the game-designer drafts and you write the GDD — the pattern /team-level and /team-narrative use. At the Phase 1 decision point, present the draft and ask via AskUserQuestion: "May I write the design document to design/gdd/[feature].md?" Write it on approval; nothing is written under design/ before that answer.

Phase 2: Architecture

Delegate to gameplay-programmer (with ai-programmer if AI is involved):

• Review the design document
• Design the code architecture: class structure, interfaces, data flow
• Identify integration points with existing systems
• Output: architecture sketch with file list and interface definitions

Then spawn the primary engine specialist to validate the proposed architecture:

• Is the class/node/component structure idiomatic for the pinned engine? (e.g., Godot node hierarchy, Unity MonoBehaviour vs DOTS, Unreal Actor/Component design)
• Are there engine-native systems that should be used instead of custom implementations?
• Any proposed APIs that are deprecated or changed in the pinned engine version?
• Output: engine architecture notes — incorporate into the architecture before Phase 3 begins

If no engine is configured, skip the specialist spawn. Record Engine validation: NOT ASSESSED — no engine configured (`engine.name` unset in `project.yaml`) in this run's output. A skipped check that says nothing is indistinguishable from a check that passed.

Use AskUserQuestion:

• Prompt: "Architecture sketch complete. Approve to proceed with parallel implementation."
• Options:
  • [A] Proceed — spawn implementation agents (gameplay-programmer, ai-programmer, technical-artist, sound-designer)
  • [B] Revise the architecture first — I'll describe what needs to change
  • [C] Stop here — I'll continue later

Only spawn implementation agents if user selects [A]. (In guided/autonomous mode this architecture gate is a normal phase transition — proceed to implementation unless the architecture sketch came back BLOCKED, recording the decision via log_decision in autonomous mode. The gate is not a release- critical or irreversible decision, so it follows the standard pipeline rule.)

Phase 3: Implementation (parallel where possible)

Delegate in parallel:

• gameplay-programmer: Implement core combat mechanic code
• ai-programmer: Implement AI behaviors (if the feature involves NPC reactions)
• technical-artist: Create VFX and shader effects
• sound-designer: Define audio event list and mixing notes, drafted to production/combat/[feature]-audio-events.md

The code, VFX and shader work is outside the bounded write exception: each of those agents first returns the files it will create or change, you ask once for the whole set, and they write only after a yes (File Write Protocol).

Phase 4: Integration

• Wire together gameplay code, AI, VFX, and audio
• Ensure all tuning knobs are exposed and data-driven
• Verify the feature works with existing combat systems

Gate: Use AskUserQuestion to present the integration result and confirm before proceeding to Phase 5.

Phase 5: Validation

Delegate to qa-tester:

• Write test cases from the acceptance criteria
• Test all edge cases documented in the design
• Verify performance impact is within budget
• File bug reports for any issues found

Phase 6: Sign-off

• Collect results from all team members
• Report feature status: COMPLETE / NEEDS WORK / BLOCKED
• List any outstanding issues and their assigned owners

Error Recovery Protocol

First, verify the artifact. If the return contract named a path, check the path exists before treating the phase as done — a named artifact that is not on disk is a failed phase, however fluent the response reads. An agent can burn a full phase and return a plausible preamble having written nothing, which is neither BLOCKED nor an error nor "cannot complete", so the trigger below never fires. Resume it naming the unmet contract; the context is usually still there.

If any spawned agent returns BLOCKED, errors, or cannot complete: surface it immediately, don't proceed past a dependency it blocks, and always produce a partial report. A skipped agent's section stays a named gap — never fill it with content of your own. Full procedure: .claude/docs/error-recovery-protocol.md.

Common blockers:

• Input file missing (story not found, GDD absent) → redirect to the skill that creates it
• ADR status is Proposed → do not implement; once it is decided, accept it with /architecture-decision accept ADR-NNNN
• Scope too large → split into two stories via /create-stories
• Conflicting instructions between ADR and story → surface the conflict, do not guess

File Write Protocol

All file writes (design drafts, implementation files, test cases) are delegated to sub-agents spawned via Agent, under two rules:

• Drafts, sketches and QA artifacts — the path table's destinations under production/, docs/ or tests/ — follow the bounded exception documented above under "Why this does not violate the Collaboration Protocol": the path is one you named, the artifact is new, and the phase is gated by an AskUserQuestion. The sub-agent writes them without a per-write prompt.
• Implementation files — Phase 3's code, VFX and shader files, and any Phase 4 integration edits, under the code root and assets/ — are outside that exception, as the agents' own files say. Each implementing agent first returns the files it will create or change with a one-line summary each; ask once for the whole set ("May I have [agents] write these [N] files?") and have them write only after a yes. An edit to an existing file is always on that list, never implied by the pre-Phase 3 gate.

The one exception is the design document: the orchestrator writes design/gdd/[feature].md itself, from the game-designer's draft, after its own "May I write …?" prompt (Phase 1). It writes no other file.

Output

A summary report covering: design completion status, implementation status per team member, test results, and any open issues.

Verdict: COMPLETE — combat feature designed, implemented, and validated.

If the engine validation was skipped (Phase 2, no engine configured), the verdict says so — never a plain COMPLETE:

Verdict: COMPLETE — engine validation NOT ASSESSED ([reason]) — combat feature designed, implemented, and validated; the engine specialist never reviewed the architecture.

Verdict: NEEDS WORK — every phase ran, but Phase 5 validation left failures or open bugs unresolved; the report lists each with its owner.

Verdict: BLOCKED — one or more phases could not complete, or an agent was skipped (.claude/docs/error-recovery-protocol.md step 5); partial report produced with unresolved items listed.

Next Steps

• Run /code-review on the implemented combat code before closing stories.
• Run /balance-check to validate combat formulas and tuning values.
• Run /team-polish if VFX, audio, or performance polish is needed.