shine-complete-milestone

Archive completed milestones into versioned ROADMAP and REQUIREMENTS files.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-complete-milestone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shine-complete-milestone
Source: https://github.com/diShine-digital-agency/SHINE-Code-System/tree/main/skills/shine-complete-milestone
Command: npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-complete-milestone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed milestones and prepare artifacts for next versions by capturing a full historical record and updating project state.

Core Features & Use Cases

  • Archive milestone artifacts (ROADMAP.md and REQUIREMENTS.md) into .planning/milestones/v{{version}}-ROADMAP.md and .planning/milestones/v{{version}}-REQUIREMENTS.md.
  • Update PROJECT.md and STATE.md to reflect current shipped version and next milestone goals.
  • Ensure governance traceability by preserving prior milestone content and generating a concise one-line ROADMAP entry with a link.

Quick Start

Archive milestone by running the complete-milestone workflow with a version parameter to archive ROADMAP and REQUIREMENTS and update PROJECT.md

Frequently Asked Questions about shine-complete-milestone

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

FAQPage Schema
How do I archive completed project milestones and preserve roadmap history?

To archive completed project milestones, generate milestone-specific ROADMAP and REQUIREMENTS archives under .planning/milestones/ and update PROJECT.md and STATE.md. This preserves prior content and creates a one-line ROADMAP entry with a governance link to the full record.

What is the best way to prepare project state for a new version after finishing a milestone?

Preparing project state for a new version involves updating PROJECT.md and STATE.md to reflect the shipped version and next milestone goals. The complete-milestone workflow validates readiness, extracts accomplishments, and generates fresh requirements for the upcoming version.

How does milestone governance traceability work when archiving project requirements?

Milestone governance traceability works by preserving prior ROADMAP and REQUIREMENTS content in versioned archives under .planning/milestones/. It generates a concise one-line ROADMAP entry containing a link to the full historical milestone record for complete traceability.

Do I need a specific project structure to run the complete-milestone workflow?

Running the complete-milestone workflow requires a project structure containing .planning/milestones/, PROJECT.md, STATE.md, and existing ROADMAP.md and REQUIREMENTS.md files. The skill validates milestone readiness against these artifacts before archiving and updating project state.

Can I extract key accomplishments from a completed milestone automatically?

Yes, you can automatically extract key accomplishments from a completed milestone. The complete-milestone workflow validates milestone readiness, extracts key accomplishments, and uses them to create a one-line ROADMAP entry linking to the full milestone record for governance.

Why does milestone archiving preserve prior roadmap and requirements content?

Milestone archiving preserves prior ROADMAP and REQUIREMENTS content to ensure governance traceability and prevent historical data loss. It archives these files under .planning/milestones/v{{version}} while updating PROJECT.md and STATE.md to prepare fresh requirements for the next milestone.