milestone-review

Generates milestone progress reviews with feature completeness, quality metrics, and go/no-go recommendations.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill milestone-review-onemanking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: milestone-review
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/milestone-review
Command: npx skills add https://github.com/onemanking/the-operator --skill milestone-review-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project leads lack a consolidated view of milestone health, forcing them to manually gather sprint reports, bug counts, code health markers, and risk data before deciding whether a milestone is on track. ## Core Features & Use Cases - Feature Completeness Tracking: Categorizes features as fully complete, partially complete, or not started with acceptance criteria and cut-impact analysis. - Quality and Code Health Metrics: Aggregates open bug counts by severity, test coverage, and TODO/FIXME/HACK marker counts across the codebase. - Go/No-Go Assessment: Produces a velocity analysis, scope recommendations, and a GO, CONDITIONAL GO, or NO-GO recommendation with action items. - Use Case: At the end of a sprint cycle, a product manager invokes the review for the current milestone to decide which features to protect, which to cut, and whether the release date is still achievable. ## Quick Start Ask the assistant to run a milestone review for the current milestone and include a go/no-go recommendation.

Frequently Asked Questions about milestone-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a milestone progress review report?

Invoke the milestone-review skill with a milestone name or 'current' as the argument. It reads the milestone definition, all related sprint reports, and the risk register, then outputs a structured Markdown review with completeness tables and a go/no-go recommendation.

What data sources does a milestone review use?

The review reads milestone definitions from production/milestones, sprint reports from production/sprints, and the risk register from production/risk-register. It also scans the codebase for TODO, FIXME, and HACK markers to measure code health.

How is the go/no-go recommendation determined?

The recommendation combines feature completeness, open bug counts by severity, velocity trends across sprints, and risk register status. The output is GO, CONDITIONAL GO with listed conditions, or NO-GO, each with a written rationale.

Can I review a past milestone instead of the current one?

Yes, pass the milestone name as the argument instead of 'current'. The skill reads that milestone's definition and its associated sprint reports to produce the same structured review format.

What happens if sprint reports or the risk register are missing?

The review depends on files in production/milestones, production/sprints, and production/risk-register. Missing inputs limit the corresponding sections, so ensure these directories are populated before running the review.