milestone-tracker

Compare milestone snapshots and generate status notifications from memory/milestones.md.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill milestone-tracker-atrium-hermes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: milestone-tracker
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/milestone-tracker
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill milestone-tracker-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Milestone-tracker automates the monitoring of progress toward defined milestones across repositories, memory stores, and product goals, reducing manual tracking and missed alerts.

Core Features & Use Cases

  • Load milestone configurations from memory/milestones.md, compare with last run, and classify statuses (crossed, approaching, stalled, on-track).
  • Generate and route notifications when notable changes occur, helping teams stay aligned without manual checks.
  • Store last run state in memory to enable incremental progress tracking across weekly runs.
  • Use Case: A growth team tracks features across multiple repos and receives weekly summaries of progress, risks, and required actions.

Quick Start

Run the milestone-tracker to load milestones, compare current state, and generate notifications.

Frequently Asked Questions about milestone-tracker

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

FAQPage Schema
How do I track milestone progress across multiple repositories?

Milestone tracking across repositories loads configurations from a memory file, compares current snapshots against the last run, classifies status as crossed or stalled, and outputs notifications while updating state.

Can I get alerts when product milestones approach or stall?

Alerts for approaching or stalled milestones are generated by comparing current snapshots to the previous run, classifying status changes, and routing notifications to keep teams aligned without manual checks.

How does incremental milestone tracking work on a weekly cadence?

Incremental tracking on a weekly cadence stores the last run state in memory, compares the current snapshot to that state on each run, and updates the memory file to enable continuous progress monitoring.

What is the best way to automate cross-team milestone monitoring?

Automated cross-team milestone monitoring reads a defined milestone configuration file, detects progress changes since the last execution, and produces weekly summaries of progress, risks, and required actions.

Do I need a specific file format to define milestones for tracking?

Milestone definitions require a markdown file stored at memory/milestones.md, which the tracker reads to compare current snapshots, classify statuses, and generate notifications.

Why does milestone tracking show no status changes between runs?

No status changes appear when current snapshots match the stored last run state, meaning milestones remain on-track; the tracker only flags crossed, approaching, or stalled statuses when deviations occur.