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 |
|---|