How do I install the Milestone Review skill?

Run npx skillmds add majiayu000/milestone-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Milestone Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Milestone Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Milestone Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Milestone Review?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Milestone Review by majiayu000 — Agent Skill

Name: Milestone Review
Rating: 4.5 (4 reviews)
Author: majiayu000

Milestone Review

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.

majiayu000 e7faf6d 2 files · 3.3 KB Updated Sep 9, 2026 567 repo stars

File contents

When this skill is invoked:

Read the milestone definition from production/milestones/.
Read all sprint reports for sprints within this milestone from production/sprints/.
Scan the codebase for TODO, FIXME, HACK markers that indicate incomplete work.
Check the risk register at production/risk-register/.
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
| 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 |
|---|--------|-------|----------|

---name: milestone-reviewdescription: 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.--- 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 | |---|--------|-------|----------| ```

Frequently asked questions