Files
Claude-Code-Game-Studios/.claude/docs/templates/sprint-plan.md
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

2.2 KiB

Sprint [N] -- [Start Date] to [End Date]

Sprint Goal

[One sentence: what does this sprint achieve toward the current milestone?]

Milestone Context

  • Current Milestone: [Name]
  • Milestone Deadline: [Date]
  • Sprints Remaining: [N]

Capacity

Resource Available Days Allocated Buffer (20%) Remaining
Programming
Design
Art
Audio
QA
Total

Tasks

Must Have (Critical Path)

ID Task Agent/Owner Est. Days Dependencies Acceptance Criteria Status
S[N]-001 None Not Started
S[N]-002 S[N]-001 Not Started

Should Have

ID Task Agent/Owner Est. Days Dependencies Acceptance Criteria Status
S[N]-010 Not Started

Nice to Have (Cut First)

ID Task Agent/Owner Est. Days Dependencies Acceptance Criteria Status
S[N]-020 Not Started

Carryover from Sprint [N-1]

Original ID Task Reason for Carryover New Estimate Priority Change

Risks to This Sprint

Risk Probability Impact Mitigation Owner

External Dependencies

Dependency Status Impact if Delayed Contingency

Definition of Done

  • All Must Have tasks completed and passing acceptance criteria
  • No S1 or S2 bugs in delivered features
  • Code reviewed and merged to develop
  • Design documents updated for any deviations from spec
  • Test cases written and executed for all new features
  • Asset naming and format standards met

Daily Status Tracking

Day Tasks Completed Tasks In Progress Blockers Notes
Day 1
Day 2
Day 3