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>
92 lines
2.5 KiB
Markdown
92 lines
2.5 KiB
Markdown
---
|
|
name: milestone-review
|
|
description: "Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline."
|
|
argument-hint: "[milestone-name|current]"
|
|
user-invocable: true
|
|
allowed-tools: Read, Glob, Grep, Write
|
|
---
|
|
|
|
When this skill is invoked:
|
|
|
|
1. **Read the milestone definition** from `production/milestones/`.
|
|
|
|
2. **Read all sprint reports** for sprints within this milestone from
|
|
`production/sprints/`.
|
|
|
|
3. **Scan the codebase** for TODO, FIXME, HACK markers that indicate
|
|
incomplete work.
|
|
|
|
4. **Check the risk register** at `production/risk-register/`.
|
|
|
|
5. **Generate the milestone review**:
|
|
|
|
```markdown
|
|
# Milestone Review: [Milestone Name]
|
|
|
|
## Overview
|
|
- **Target Date**: [Date]
|
|
- **Current Date**: [Today]
|
|
- **Days Remaining**: [N]
|
|
- **Sprints Completed**: [X/Y]
|
|
|
|
## Feature Completeness
|
|
|
|
### Fully Complete
|
|
| Feature | Acceptance Criteria | Test Status |
|
|
|---------|-------------------|-------------|
|
|
|
|
### Partially Complete
|
|
| Feature | % Done | Remaining Work | Risk to Milestone |
|
|
|---------|--------|---------------|------------------|
|
|
|
|
### Not Started
|
|
| Feature | Priority | Can Cut? | Impact of Cutting |
|
|
|---------|----------|----------|------------------|
|
|
|
|
## Quality Metrics
|
|
- **Open S1 Bugs**: [N] -- [List]
|
|
- **Open S2 Bugs**: [N]
|
|
- **Open S3 Bugs**: [N]
|
|
- **Test Coverage**: [X%]
|
|
- **Performance**: [Within budget? Details]
|
|
|
|
## Code Health
|
|
- **TODO count**: [N across codebase]
|
|
- **FIXME count**: [N]
|
|
- **HACK count**: [N]
|
|
- **Technical debt items**: [List critical ones]
|
|
|
|
## Risk Assessment
|
|
| Risk | Status | Impact if Realized | Mitigation Status |
|
|
|------|--------|-------------------|------------------|
|
|
|
|
## Velocity Analysis
|
|
- **Planned vs Completed** (across all sprints): [X/Y tasks = Z%]
|
|
- **Trend**: [Improving / Stable / Declining]
|
|
- **Adjusted estimate for remaining work**: [Days needed at current velocity]
|
|
|
|
## Scope Recommendations
|
|
### Protect (Must ship with milestone)
|
|
- [Feature and why]
|
|
|
|
### At Risk (May need to cut or simplify)
|
|
- [Feature and risk]
|
|
|
|
### Cut Candidates (Can defer without compromising milestone)
|
|
- [Feature and impact of cutting]
|
|
|
|
## Go/No-Go Assessment
|
|
|
|
**Recommendation**: [GO / CONDITIONAL GO / NO-GO]
|
|
|
|
**Conditions** (if conditional):
|
|
- [Condition 1 that must be met]
|
|
- [Condition 2 that must be met]
|
|
|
|
**Rationale**: [Explanation of the recommendation]
|
|
|
|
## Action Items
|
|
| # | Action | Owner | Deadline |
|
|
|---|--------|-------|----------|
|
|
```
|