milestone-complete

Update project documentation files after completing a milestone.

2|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/rfhayn/forager --skill milestone-complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: milestone-complete
Source: https://github.com/rfhayn/forager/tree/main/.claude/skills/milestone-complete
Command: npx skills add https://github.com/rfhayn/forager --skill milestone-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of marking project milestones as complete, ensuring documentation is kept up-to-date without manual intervention.

Core Features & Use Cases

  • Automated Documentation Update: Update core documentation files automatically, such as current-story.md and next-prompt.md.
  • Branch Tracking: Keep track of the current branch and uncommitted changes during milestone completion.
  • File Management: Archive branch-specific next-prompt files and update the project index and insights log.

Quick Start

To mark a milestone complete, run the command: milestone-complete "M#.#"

Frequently Asked Questions about milestone-complete

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

FAQPage Schema
How do I automate project documentation updates when completing a milestone?

Automating milestone documentation updates involves running a single command that identifies and normalizes a milestone identifier, then triggers updates across multiple project documentation files automatically within your source control repository.

Can I update current-story.md and next-prompt.md automatically when a milestone is done?

Yes, automated milestone completion can update core documentation files such as current-story.md and next-prompt.md automatically, while also archiving branch-specific next-prompt files and updating the project index and insights log.

Does milestone tracking with document automation work with uncommitted source control changes?

Yes, milestone tracking with document automation keeps track of the current branch and uncommitted changes during the milestone completion process, ensuring repository state is monitored while documentation updates are triggered.

What permissions do I need to run automated milestone tracking scripts on a repository?

Running automated milestone tracking scripts requires access to the project's source code repository and the appropriate permissions to modify it, as the script automates updates across multiple documentation files within the repository.

How do I archive branch-specific next-prompt files during milestone completion?

To archive branch-specific next-prompt files during milestone completion, the automated script processes the given milestone identifier, normalizes it, and handles file management by archiving these files while updating the project index and insights log.