milestone-tracker

To automate weekly milestone tracking, this skill reads targets from memory/milestones.md, pulls GitHub star counts via the gh CLI, and updates the file after each run. It classifies progress as crossed, approaching, stalled, or on-track.

Stall detection in growth tracking identifies milestones lacking progress by evaluating thresholds and stall streaks from persistent memory. It then conditionally generates a notification payload for delivery when targets are stalled.

Yes, you can track enabled skill counts alongside manual operator targets. The skill reads enabled skills from aeon.yml while supporting operator-managed manual milestones, consolidating everything into the memory/milestones.md file.

Automated progress notifications without approval loops are generated by writing conditional payloads for the ./notify tool to deliver. Notifications trigger only when milestones are crossed, approaching, or stalled.

No, you do not need to manually create the milestones.md file. The skill automatically creates a seed file in the memory directory if the file is missing during its initial run.

Limitations of using persistent memory files for weekly reporting include reliance on local markdown state management and requiring the gh CLI for GitHub API access. Operations are scheduling-friendly but depend on file system persistence.