gpd-complete-milestone

Archive completed research milestones and prepare roadmap for the next investigation phase.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-complete-milestone-michaelsengineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gpd-complete-milestone
Source: https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics/tree/main/.agents/skills/gpd-complete-milestone
Command: npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-complete-milestone-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research projects accumulate phases, plans, and requirements that become hard to track once a milestone finishes. This Skill closes out a completed research milestone by archiving the roadmap and requirements, generating a research digest, evolving the project state, and tagging the release in git so the next stage starts from a clean, well-documented baseline. ## Core Features & Use Cases - Milestone Archival: Extracts full milestone details into .gpd/milestones/v[X.Y]-ROADMAP.md and v[X.Y]-REQUIREMENTS.md, keeping the active ROADMAP.md constant-size. - Research Digest Generation: Composes a structured RESEARCH-DIGEST.md with narrative arc, key results, methods, convention evolution, figures registry, open questions, and dependency graph for downstream paper writing. - Project Evolution Review: Moves completed requirements to Validated in PROJECT.md, audits key decisions, updates context, and refreshes STATE.md. - Git Integration: Handles branch merging (squash or no-ff), creates annotated version tags, and commits milestone artifacts. - Use Case: After finishing all phases of a v1.0 model derivation milestone, run this Skill to archive the roadmap, generate the research digest, tag v1.0 in git, and prepare handoff notes for the v1.1 validation stage. ## Quick Start Ask the AI to complete milestone v1.0 by archiving the roadmap and requirements, generating the research digest, and tagging the release in git.

Frequently Asked Questions about gpd-complete-milestone

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

FAQPage Schema
How do I complete a research milestone in a GPD project?▼

Run the complete-milestone workflow with the target version, for example v1.0. It verifies all phase plans have summaries via roadmap analyze, archives ROADMAP.md and REQUIREMENTS.md into .gpd/milestones/, generates a research digest, and tags the release in git.

What files are created when a milestone is archived?▼

The workflow creates v[X.Y]-ROADMAP.md and v[X.Y]-REQUIREMENTS.md under .gpd/milestones/, plus a RESEARCH-DIGEST.md in a versioned subdirectory. It also appends an entry to MILESTONES.md and updates STATE.md and PROJECT.md.

Does completing a milestone delete the phase directories?▼

No, phase directories under .gpd/phases/ are preserved as raw research history and accumulate across milestones. Phase numbering continues across milestones, so v1.0 might use phases 1-4 and v1.1 phases 5-8.

When should I create a research milestone versus just finishing a phase?▼

Create a milestone only for complete, self-contained research results that could be presented or published, such as a finished derivation or validated numerical implementation. Do not create milestones for individual phase completions or exploratory calculations.

What happens to REQUIREMENTS.md after milestone completion?▼

REQUIREMENTS.md is archived to .gpd/milestones/v[X.Y]-REQUIREMENTS.md and then deleted from the active .gpd/ directory, but only after verifying the archive exists. A fresh requirements file is created for the next research stage.

How does the milestone workflow handle git branches?▼

It detects the branching strategy (per-phase or per-milestone) from the GPD config and offers options to squash merge, merge with history, delete without merging, or keep branches. It then creates an annotated git tag for the version.