mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 04:51:46 +00:00
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>
This commit is contained in:
69
.claude/docs/templates/post-mortem.md
vendored
Normal file
69
.claude/docs/templates/post-mortem.md
vendored
Normal file
@@ -0,0 +1,69 @@
|
||||
# Post-Mortem: [Milestone/Project Name]
|
||||
|
||||
## Document Status
|
||||
- **Date**: [Date]
|
||||
- **Facilitator**: producer
|
||||
- **Participants**: [List of agents/people involved]
|
||||
- **Period Covered**: [Start date] to [End date]
|
||||
|
||||
## Summary
|
||||
[2-3 sentence summary of what this milestone/project accomplished]
|
||||
|
||||
## Goals vs Results
|
||||
|
||||
| Goal | Target | Result | Status |
|
||||
| ---- | ------ | ------ | ------ |
|
||||
| [Goal 1] | [Metric] | [Actual] | [Met / Partially / Missed] |
|
||||
|
||||
## Timeline
|
||||
|
||||
| Date | Event | Impact |
|
||||
| ---- | ----- | ------ |
|
||||
| [Date] | [What happened] | [How it affected the project] |
|
||||
|
||||
## What Went Well
|
||||
|
||||
### [Category 1: e.g., Technical Execution]
|
||||
**What**: [Description]
|
||||
**Why it worked**: [Root cause of success]
|
||||
**How to repeat**: [What to keep doing]
|
||||
|
||||
### [Category 2: e.g., Team Coordination]
|
||||
**What**: [Description]
|
||||
**Why it worked**: [Root cause]
|
||||
**How to repeat**: [Action]
|
||||
|
||||
## What Went Poorly
|
||||
|
||||
### [Category 1: e.g., Scope Management]
|
||||
**What**: [Description]
|
||||
**Root cause**: [Why this happened]
|
||||
**Impact**: [Time/quality/morale cost]
|
||||
**Prevention**: [How to avoid next time]
|
||||
|
||||
### [Category 2]
|
||||
[Same structure]
|
||||
|
||||
## Key Metrics
|
||||
|
||||
| Metric | Target | Actual | Notes |
|
||||
| ------ | ------ | ------ | ----- |
|
||||
| Tasks completed | [N] | [N] | |
|
||||
| Bugs found | — | [N] | |
|
||||
| Bugs fixed | — | [N] | |
|
||||
| Estimation accuracy | 100% | [N%] | |
|
||||
| Scope changes | 0 | [N] | |
|
||||
|
||||
## Lessons Learned
|
||||
|
||||
1. **[Lesson]**: [Explanation and how it changes future work]
|
||||
2. **[Lesson]**: [Explanation]
|
||||
|
||||
## Action Items
|
||||
|
||||
| # | Action | Owner | Deadline | Status |
|
||||
| - | ------ | ----- | -------- | ------ |
|
||||
| 1 | [Action] | [Who] | [When] | [Open/Done] |
|
||||
|
||||
## Acknowledgments
|
||||
[Call out exceptional contributions]
|
||||
Reference in New Issue
Block a user