milestone-review
Skill1 starsChanged 30 days agoMITView on GitHub
Milestone progress review — completeness, quality metrics, risk, go/no-go recommendation. At checkpoints or before a deadline.
18 other projects use a version of this, 11 of them edited.
Adopted by
Most recently taken up by
- chuanglibs/Claude-Code-Game-Studios-Codexedited, first seen Nov 15, 2026
- Donchitos/Claude-Code-Game-Studiosedited, first seen Nov 9, 2026
- striderZA/OpenCodeGameStudiosedited, first seen Nov 4, 2026
- Cassandra-Collective/Ephesustheir own version, first seen Nov 1, 2026
- zajca/pohunektheir own version, first seen Oct 13, 2026
- scotidev/GameDevStudioedited, first seen Oct 9, 2026
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 11
- Donchitos/Claude-Code-Game-Studios★ 39k97% same
- striderZA/OpenCodeGameStudios★ 12475% same
- tranhieutt/software_development_department★ 7151% same
- CoralGame/Claude-Code-Game-Studios★ 1971% same
- dawn840705/codex-code-studios★ 1775% same
- lilangMax/ClaudeCodeGameStudios★ 876% same
- hongyuanc/codex-game-studios★ 565% same
- chuanglibs/Claude-Code-Game-Studios-Codex★ 180% same
- dawn840705/claude-code-studios★ 176% same
- HunLuanZhiZhu/Game-Studios-Plugin★ 180% same
1 more not listed
Wrote their own version · 7
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- cenconq25/claude-code-app-studio★ 40same name
- CodePhobiia/claude-roblox-game-studio★ 9same name
- zajca/pohunek★ 9same name
- timjrobinson/Claude-Code-Construction-Manager★ 4same name
- Cassandra-Collective/Ephesus★ 2same name
- mertefesensoy/Ephesus★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository153 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CCGS Skill Testing Framework/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- design/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- adoptSkill
- architecture-decisionSkill
- architecture-reviewSkill
- art-bibleSkill
- asset-auditSkill
- asset-specSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- bug-triageSkill
- changelogSkill
- code-reviewSkill
- consistency-checkSkill
- content-auditSkill
- create-architectureSkill
- create-control-manifestSkill
- create-epicsSkill
- create-storiesSkill
- day-one-patchSkill
- design-reviewSkill
- design-systemSkill
- dev-storySkill
- estimateSkill
- gate-checkSkill
- helpSkill
- hotfixSkill
- launch-checklistSkill
- localizeSkill
- map-systemsSkill
- milestone-reviewSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- playtest-reportSkill
- project-stage-detectSkill
- propagate-design-changeSkill
- prototypeSkill
- qa-planSkill
- quick-designSkill
- regression-suiteSkill
- release-checklistSkill
- retrospectiveSkill
- reverse-documentSkill
- review-all-gddsSkill
- scope-checkSkill
- security-auditSkill
- settingsSkill
- setup-engineSkill
- skill-improveSkill
- skill-testSkill
- smoke-checkSkill
- soak-testSkill
- sprint-planSkill
- sprint-statusSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 6 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
If any input required for a section is ABSENT, that section is
- Very specific: line 28
NOT ASSESSED — NO DATA: Do not estimate it, do not infer it from an adjacent artifact, and do not leave a mandated cell to be filled by … - Distinctive: line 31
If every required input is ABSENT, stop and report
- Very specific: line 55
Every AskUserQuestion call follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and …
- Very specific: line 63
Read the milestone definition from production/milestones/ if it exists.
- Very specific: line 118
Check the risk register at production/risk-register/ if it exists (hand-authored from .claude/docs/templates/risk-register-entry.md.
- Very specific: line 213
Before generating the Go/No-Go recommendation, spawn producer via Agent using gate PR-MILESTONE …
- Very specific: line 219
If OFF TRACK, use AskUserQuestion before generating the recommendation:
- Very specific: line 226
If AT RISK, use AskUserQuestion:
- Distinctive: line 233
If NOT ASSESSED: name the missing input — it is not ON TRACK, and never recommend GO on it.
- Distinctive: line 235
Do not issue a GO against an OFF TRACK verdict.
- Very specific: line 243
Ask: "May I write this to production/milestones/[milestone-name]-review.md?"
- Distinctive: line 245
If yes, write the file, creating the directory if needed.
- Distinctive: line 247
If no, stop here. Verdict: BLOCKED — user declined write.
- Very specific: line 253
Run /gate-check for a formal phase gate verdict if this milestone marks a development phase boundary.
- Very specific: line 254
Run /sprint-plan to adjust the next sprint based on the scope recommendations above (at workflow: minimal, which has no sprints, adjust the …
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,workflow
Resolved above — use as-is; --review overrides review_mode for this run. No
block → defaults in .claude/docs/config-resolution.md.
Milestone Review
Insufficient input — check this before producing any report
If the inputs this skill needs do not exist, the answer is "could not run" — not a filled-in report. Check first, and stop if the check fails.
- List the inputs this skill reads (data files, prior reports, profiler output, test results, registries, source code).
- For each, record
FOUNDorABSENT— not "assumed present". - If any input required for a section is ABSENT, that section is
NOT ASSESSED — NO DATA. Do not estimate it, do not infer it from an adjacent artifact, and do not leave a mandated cell to be filled by whoever reads the template next. - If every required input is ABSENT, stop and report
NOT ASSESSED — NO DATAas the whole verdict, naming what was missing and which skill produces it.
A verdict of NOT ASSESSED is a success. It is the correct, useful answer to
"what does the data say?" when there is no data. The failure mode this prevents is
specific: a report whose verdict enum has no "could not run" state produces
false clean passes — an asset audit returning COMPLIANT on a project with no
assets and no standards, or a performance profile reporting ">99% headroom against
a 16.67ms budget" with zero profiler data and no budget ever set.
Absence of evidence is never evidence of absence. A scan that finds no matches because there are no files to scan has not verified anything. Say which of the two happened — a reader cannot tell from a green result.
Phase 0: Parse Arguments
Extract the milestone name (current or a specific name).
See .claude/docs/director-gates.md for the full check pattern. Individual gate definitions live in .claude/docs/director-gates/[gate-id].md — the spawned agent reads its own gate file; do not read it in the parent session.
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Phase 1: Load Milestone Data
Read the milestone definition from production/milestones/ if it exists. If the
argument is current, use the most recently modified milestone file.
No skill writes
production/milestones/— definitions are authored by hand from.claude/docs/templates/milestone-definition.md, so most projects have none. When the directory is absent or empty, say so and review against the sprint reports alone; do not fabricate a definition. Take care withcurrent: this skill writes its own output as[milestone-name]-review.md, so a most-recently-modified match can be a previous review rather than a definition. Skip files ending-review.mdwhen selecting.
Gather the sprint reports for sprints within this milestone from
production/sprints/. Establish the denominator (glob them, count N), then
scan the sections a milestone review actually aggregates rather than reading each
report whole:
Grep pattern="^## (Sprint Goal|Capacity|Tasks|Carryover|Risks|Progress|Burndown Assessment|Emerging Risks|Definition of Done)" glob="production/sprints/sprint-*.md" output_mode="content" -A 12These alternates are copied from
/sprint-plan's emitted headings — keep them in sync with it, not with what a milestone review wishes existed. The previous pattern asked forSummary|Goal|Velocity|Completed|Blockers| Retrospective, none of which/sprint-planwrites (it emits## Sprint Goal, not## Goal). OnlyCarryovermatched — and that was the trap: a non-zero match count meant the zero-match escape hatch below could never fire, so every milestone review silently aggregated carryover tables and nothing else while reporting full coverage.
Full-read a single sprint report when its scanned sections point outside themselves, or when it matched nothing — a zero-match report predates the template and must be read, never silently dropped from the milestone's history. Report any sprint that contributed nothing: a milestone summary that quietly omits a sprint understates the work and the slippage both.
Blocked stories — the Blocked table and the blocked story count passed to
PR-MILESTONE — are not in the sprint reports' scanned sections. Read them where
they are recorded: the status: blocked stories in production/sprint-status.yaml
(with their blocker field) and, for stories outside that sprint, one grep:
Grep pattern="^> \*\*Status\*\*: Blocked|BLOCKED:" glob="production/epics/**/story-*.md" output_mode="content"Each blocked story goes in the Blocked table under the feature its epic folder
implements, with its blocker (the yaml blocker field or the story's BLOCKED:
note). With no story files and no sprint-status.yaml, the Blocked table and the
blocked story count are NOT ASSESSED — NO DATA, not zero.
Phase 2: Scan Codebase Health
- Scan for
TODO,FIXME,HACKmarkers that indicate incomplete work - Count open bugs by severity for Quality Metrics from
production/qa/bugs/(one grep of the**Severity**and**Status**lines, as/bug-triagedoes); with no bug files, the bug lines areNOT ASSESSED — NO DATA, not zero - Check the risk register at
production/risk-register/if it exists (hand-authored from.claude/docs/templates/risk-register-entry.md; no skill writes it, so absence is normal — note it rather than skipping risk assessment silently)
Phase 3: Generate the Milestone Review
# Milestone Review: [Milestone Name]
## Overview
- **Target Date**: [Date]
- **Current Date**: [Today]
- **Days Remaining**: [N]
- **Sprints Completed**: [X/Y]
## Feature Completeness
### Fully Complete
Only a feature whose Status is `Complete` goes here or counts toward the completion percentage; a Deferred feature stays in its denominator, named with the milestone it moved to.
| Feature | Acceptance Criteria | Test Status |
|---------|-------------------|-------------|
### Partially Complete
| Feature | % Done | Remaining Work | Risk to Milestone |
|---------|--------|---------------|------------------|
### Blocked
A started feature whose stories are Blocked goes here, not under Partially
Complete — name the blocker, so the review says why it stalled, not only that
the count moved.
| Feature | Blocked Stories | Blocker | Next Action / Owner |
|---------|----------------|---------|---------------------|
### 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**: [NOT ASSESSED / 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 |
|---|--------|-------|----------|Phase 3b: Producer Risk Assessment
Review mode check — apply before spawning PR-MILESTONE:
solo→ skip. Note: "PR-MILESTONE skipped — Solo mode." Present the Go/No-Go section without a producer verdict.lean→ skip (not a PHASE-GATE). Note: "PR-MILESTONE skipped — Lean mode." Present the Go/No-Go section without a producer verdict.full→ spawn as normal.
Before generating the Go/No-Go recommendation, spawn producer via Agent using gate PR-MILESTONE (.claude/docs/director-gates/pr-milestone.md).
Pass: milestone name and target date, current completion percentage, blocked story count, velocity data from sprint reports (if available), list of cut candidates.
Present the producer's assessment inline within the Go/No-Go section. The producer's verdict (ON TRACK / AT RISK / OFF TRACK) informs the overall recommendation.
If OFF TRACK, use AskUserQuestion before generating the recommendation:
- Prompt: "Producer verdict: OFF TRACK. The milestone is in jeopardy. This review will recommend NO-GO. How do you want to proceed?"
- Options:
[A] Accept NO-GO — generate the full review with that recommendation[B] Override to CONDITIONAL GO — I'll document the accepted risks myself[C] Stop — I want to address blockers before generating the review
If AT RISK, use AskUserQuestion:
- Prompt: "Producer verdict: AT RISK. Milestone may slip. How should the Go/No-Go section be framed?"
- Options:
[A] CONDITIONAL GO — include producer's conditions in the review[B] NO-GO — conditions cannot be met in time[C] GO — I accept the risk and want to proceed
If NOT ASSESSED: name the missing input — it is not ON TRACK, and never recommend GO on it. Supply the input and re-run PR-MILESTONE, or recommend NOT ASSESSED — or CONDITIONAL GO / NO-GO where the review's own findings call for one (the rank in .claude/docs/director-gates.md).
Do not issue a GO against an OFF TRACK verdict; issue CONDITIONAL GO only if the user explicitly selects [B] above.
Phase 4: Save Review
Present the review to the user.
Ask: "May I write this to production/milestones/[milestone-name]-review.md?"
If yes, write the file, creating the directory if needed. Verdict: COMPLETE — milestone review saved.
If no, stop here. Verdict: BLOCKED — user declined write.
Phase 5: Next Steps
- Run
/gate-checkfor a formal phase gate verdict if this milestone marks a development phase boundary. - Run
/sprint-planto adjust the next sprint based on the scope recommendations above (atworkflow: minimal, which has no sprints, adjust the brief's build order instead).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

