mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 13:01:50 +00:00
ad540fe75d
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>
109 lines
2.9 KiB
Markdown
109 lines
2.9 KiB
Markdown
---
|
|
name: sprint-plan
|
|
description: "Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design backlogs."
|
|
argument-hint: "[new|update|status]"
|
|
user-invocable: true
|
|
allowed-tools: Read, Glob, Grep, Write, Edit
|
|
context: |
|
|
!ls production/sprints/ 2>/dev/null
|
|
---
|
|
|
|
When this skill is invoked:
|
|
|
|
1. **Read the current milestone** from `production/milestones/`.
|
|
|
|
2. **Read the previous sprint** (if any) from `production/sprints/` to
|
|
understand velocity and carryover.
|
|
|
|
3. **Scan design documents** in `design/gdd/` for features tagged as ready
|
|
for implementation.
|
|
|
|
4. **Check the risk register** at `production/risk-register/`.
|
|
|
|
For `new`:
|
|
|
|
5. **Generate a sprint plan** following this format:
|
|
|
|
```markdown
|
|
# Sprint [N] -- [Start Date] to [End Date]
|
|
|
|
## Sprint Goal
|
|
[One sentence describing what this sprint achieves toward the milestone]
|
|
|
|
## Capacity
|
|
- Total days: [X]
|
|
- Buffer (20%): [Y days reserved for unplanned work]
|
|
- Available: [Z days]
|
|
|
|
## Tasks
|
|
|
|
### Must Have (Critical Path)
|
|
| ID | Task | Agent/Owner | Est. Days | Dependencies | Acceptance Criteria |
|
|
|----|------|-------------|-----------|-------------|-------------------|
|
|
|
|
### Should Have
|
|
| ID | Task | Agent/Owner | Est. Days | Dependencies | Acceptance Criteria |
|
|
|----|------|-------------|-----------|-------------|-------------------|
|
|
|
|
### Nice to Have
|
|
| ID | Task | Agent/Owner | Est. Days | Dependencies | Acceptance Criteria |
|
|
|----|------|-------------|-----------|-------------|-------------------|
|
|
|
|
## Carryover from Previous Sprint
|
|
| Task | Reason | New Estimate |
|
|
|------|--------|-------------|
|
|
|
|
## Risks
|
|
| Risk | Probability | Impact | Mitigation |
|
|
|------|------------|--------|------------|
|
|
|
|
## Dependencies on External Factors
|
|
- [List any external dependencies]
|
|
|
|
## Definition of Done for this Sprint
|
|
- [ ] All Must Have tasks completed
|
|
- [ ] All tasks pass acceptance criteria
|
|
- [ ] No S1 or S2 bugs in delivered features
|
|
- [ ] Design documents updated for any deviations
|
|
- [ ] Code reviewed and merged
|
|
```
|
|
|
|
For `status`:
|
|
|
|
5. **Generate a status report**:
|
|
|
|
```markdown
|
|
# Sprint [N] Status -- [Date]
|
|
|
|
## Progress: [X/Y tasks complete] ([Z%])
|
|
|
|
### Completed
|
|
| Task | Completed By | Notes |
|
|
|------|-------------|-------|
|
|
|
|
### In Progress
|
|
| Task | Owner | % Done | Blockers |
|
|
|------|-------|--------|----------|
|
|
|
|
### Not Started
|
|
| Task | Owner | At Risk? | Notes |
|
|
|------|-------|----------|-------|
|
|
|
|
### Blocked
|
|
| Task | Blocker | Owner of Blocker | ETA |
|
|
|------|---------|-----------------|-----|
|
|
|
|
## Burndown Assessment
|
|
[On track / Behind / Ahead]
|
|
[If behind: What is being cut or deferred]
|
|
|
|
## Emerging Risks
|
|
- [Any new risks identified this sprint]
|
|
```
|
|
|
|
### Agent Consultation
|
|
|
|
For comprehensive sprint planning, consider consulting:
|
|
- `producer` agent for capacity planning, risk assessment, and cross-department coordination
|
|
- `game-designer` agent for feature prioritization and design readiness assessment
|