Game Studio Agent Architecture — complete setup (Phases 1-7)

48 coordinated Claude Code subagents for indie game development:
- 3 leadership agents (creative-director, technical-director, producer)
- 10 department leads (game-designer, lead-programmer, art-director, etc.)
- 23 specialist agents (gameplay, engine, AI, networking, UI, tools, etc.)
- 12 engine-specific agents (Godot, Unity, Unreal with sub-specialists)

Infrastructure:
- 34 skills (slash commands) for workflows, reviews, and team orchestration
- 8 hooks for commit validation, asset checks, session management
- 11 path-scoped rules enforcing domain-specific standards
- 28 templates for design docs, reports, and collaborative protocols

Key features:
- User-driven collaboration protocol (Question → Options → Decision → Draft → Approval)
- Engine version awareness with knowledge-gap detection (Godot 4.6 pinned)
- Phase gate system for development milestone validation
- CLAUDE.md kept under 80 lines with extracted doc imports

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude/skills/team-combat/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: team-combat
+description: "Orchestrate the combat team: coordinates game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, and qa-tester to design, implement, and validate a combat feature end-to-end."
+argument-hint: "[combat feature description]"
+user-invocable: true
+allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task
+---
+When this skill is invoked, orchestrate the combat team through a structured pipeline.
+
+## 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
+- **qa-tester** — Write test cases and validate the implementation
+
+## How to Delegate
+
+Use the Task 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: qa-tester` — Write test cases and validate implementation
+
+Always provide full context in each agent's prompt (design doc path, relevant code files, constraints). 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 in `design/gdd/` covering: 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
+
+### 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
+
+### 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
+
+### 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
+
+### 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
+
+## Output
+A summary report covering: design completion status, implementation status per team member, test results, and any open issues.