milestone-status-skill

Analyze active milestone progress and generate a structured status report.

29|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/OceanEyeFF/servo --skill milestone-status-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: milestone-status-skill
Source: https://github.com/OceanEyeFF/servo/tree/main/product/harness/skills/milestone-status-skill
Command: npx skills add https://github.com/OceanEyeFF/servo --skill milestone-status-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves the ambiguity of whether the current active milestone has actually progressed, met acceptance evidence, and reached its decision boundary without taking action or modifying repo state.

Core Features & Use Cases

  • Milestone-level progress analysis: Aggregates worktrack backlog and milestone artifacts to compute total/completed/blocked/deferred counts and completion percentage.
  • Dual acceptance model enforcement: Applies goal-driven milestone verification with worktrack completion, Milestone Gate (black-box/white-box/anti-cheat/composite acceptance), and purpose-achieved evidence coverage.
  • Handback boundary signaling: Determines whether developer handback is required and provides release/version consideration hints without performing release decisions.
  • Decision support for RepoScope.Decide: Produces structured output for downstream routing (e.g., repo-whats-next) while remaining a read-only observer/analyzer.

Quick Start

Ask your Harness to run milestone-status-skill during RepoScope.Observe to produce a structured milestone status report for the currently active milestone.

Frequently Asked Questions about milestone-status-skill

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

FAQPage Schema
How do I analyze active milestone progress and verify acceptance evidence in Codex-first repo workflows?

Milestone progress analysis aggregates worktrack backlog and milestone artifacts to compute completion percentages, while dual acceptance verification enforces worktrack completion and purpose-achieved evidence coverage to generate a deterministic milestone decision signal.

What is a handback boundary in repo governance and how does it signal developer handback?

A handback boundary determines whether developer handback is required by analyzing gate evidence and repo snapshots, providing release and version consideration hints for downstream routing without modifying repo state or executing release decisions.

How do I enforce a dual acceptance model with Milestone Gate checks for goal-driven milestones?

Dual acceptance model enforcement applies worktrack completion verification alongside Milestone Gate checks, utilizing black-box, white-box, anti-cheat, and composite acceptance methods to validate purpose-achieved evidence coverage for goal-driven milestones.

Does this milestone analysis tool execute release decisions or modify repository state during observation?

Milestone analysis operates strictly as a read-only observer during RepoScope.Observe, producing structured milestone state reports and decision support outputs for downstream routing without taking action or modifying the active repository state.

How do I generate a milestone_input_checkpoint for pipeline decision support?

Deterministic milestone_input_checkpoint generation aggregates milestone artifacts, worktrack backlog, and gate evidence into a single structured milestone state report, serving as pipeline decision support for downstream routing components like repo-whats-next.