mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-06-27 04:51:46 +00:00

Files

Donchitos ad540fe75d 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>

2026-02-13 21:04:24 +11:00

1.4 KiB

Raw Blame History

Risk: [Short Title]

Identification

ID: RISK-[NNNN]
Identified By: [Agent or person]
Date Identified: [Date]
Category: [Technical | Design | Schedule | Resource | External | Quality]

Assessment

Probability: [Very Low | Low | Medium | High | Very High]
Impact: [Minimal | Minor | Moderate | Major | Critical]
Risk Score: [Probability x Impact = Low / Medium / High / Critical]

Description

[Detailed description of the risk. What could go wrong? Under what conditions?]

Trigger Conditions

[What observable conditions would indicate this risk is materializing?]

[Condition 1]
[Condition 2]

Impact Analysis

If This Risk Materializes

Schedule Impact: [How many days/weeks of delay]
Quality Impact: [What quality degradation]
Scope Impact: [What features affected]
Cost Impact: [Resource cost of dealing with it]

Affected Systems/Features

[System 1]
[System 2]

Mitigation Strategy

Prevention (reduce probability)

[Action to prevent this risk from occurring]
[Owner and deadline for prevention action]

Contingency (reduce impact if it occurs)

[Action to take if this risk materializes]
[Owner responsible for contingency execution]

Current Status

Status: [Open | Mitigating | Occurred | Closed]
Last Reviewed: [Date]
Trend: [Increasing | Stable | Decreasing]
Notes: [Any updates]

1.4 KiB Raw Blame History