Team Combat

🌱 ShiningPlague-adopted. Originally Donchitos (barebones stub); battle-tested on a shipped Godot project. Upstream was a pointer-only file; the studio version is the full implementation — orchestration protocol, agent routing, director gates, project combat-context block.

Execution protocol: .claude/docs/templates/team-orchestrator.md Workstream state: production/workstreams/combat.md Domain code: CB

If an artifact named here is absent: say so plainly in one line, skip that step, and continue. Never invent the file to satisfy a checklist, and never fail a close because an optional artifact was never created.

Step 0: Load State + Select Activity

1. Read production/workstreams/combat.md — what's done, in-progress, next
2. Ask or infer: which ACTIVITY? (Design / Build / Content / Playtest / Review / Ship)
3. Follow the matching execution chain from team-orchestrator.md

Agent Routing — WHO to dispatch at each step

When the execution chain says "dispatch specialist," use these agents:

Gates to Fire

Project Combat Context (fill for your project)

• Combat model: [one-line summary, e.g. turn-based / real-time / hybrid] ({{GDD_PATH}} combat section)
• Core combat schemas: data/_schemas/[combat-schema].json
• Damage pipeline: src/systems/[damage-system].gd ([autoload name])
• Tunable multipliers / curves: data/_schemas/[tuning-file].json (dock-editable if the project has docks)
• Status/effect system: src/systems/[effect-system].gd ([autoload name])
• Combat ADRs: list the docs/adr/NNN-* entries that govern combat
• Note any paused combat work here so dispatched agents inherit it