milestone-review

Generate milestone progress reviews with go/no-go decisions from sprint outputs and code health signals.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid missed deadlines and last-minute surprises by producing a structured milestone progress review that consolidates feature status, code health, bugs, risks, and a clear go/no-go recommendation.

Core Features & Use Cases

  • Milestone progress scoring: Summarizes milestone completion by combining milestone definitions and sprint reports into a readiness view.
  • Quality and code health inspection: Counts TODO/FIXME/HACK markers and highlights technical debt and open bug levels to quantify stability.
  • Risk-driven decisioning: Builds a risk assessment table, recommends scope actions (protect/at risk/cut candidates), and—when in full mode—includes a producer gate verdict to drive the final recommendation.
  • Use case: At a sprint boundary or milestone deadline, review readiness for a specific milestone (e.g., “current” or a named milestone) and decide whether to proceed, proceed conditionally, or stop and address blockers.

Quick Start

Run milestone-review in lean mode for the current milestone by invoking it as: milestone-review current --review lean

Frequently Asked Questions about milestone-review

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

FAQPage Schema
How do I assess milestone readiness before a production release?

Assess milestone readiness by consolidating sprint outputs, code health markers, and risk registers into a structured go/no-go recommendation. This process evaluates feature completeness, quality metrics, and velocity trends to determine if a production release should proceed, proceed conditionally, or stop.

What is a go/no-go decision in sprint reporting?

A go/no-go decision in sprint reporting is a milestone checkpoint verdict that converts dispersed sprint outputs and code health signals into an actionable recommendation. It combines feature status, open bugs, and technical debt levels to decide whether to proceed or address blockers.

How do I generate a milestone review for a specific sprint boundary?

Generate a milestone review by invoking the tool in lean mode for the current milestone, or specify a named milestone. The tool loads milestone definitions and sprint reports from production paths, scans codebase markers, and writes a milestone review artifact to the repository.

Does milestone review evaluate code health and technical debt?

Yes, milestone review evaluates code health by scanning codebase markers and counting TODO, FIXME, and HACK instances. It highlights technical debt and open bug levels to quantify project stability and incorporate QA metrics into the final risk assessment.

Can I perform a risk assessment for production planning without external dependencies?

Yes, you can perform a risk assessment without external dependencies because the tool operates standalone. It builds a risk assessment table, identifies scope actions like protect or cut candidates, and optionally performs a producer risk gate in full mode to drive the recommendation.

What is the difference between lean and full mode for milestone progress scoring?

Lean mode summarizes milestone completion by combining definitions and sprint reports into a readiness view, while full mode additionally performs a producer risk gate to deliver a final gate verdict. Both modes scan codebase markers and write a review artifact to the repository.