gpd-add-phase

Add a new research phase to the current milestone in a GPD roadmap.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-add-phase-michaelsengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-add-phase
Source: https://github.com/MichaelsEngineering/get-physics-done-test/tree/main/.agents/skills/gpd-add-phase
Command: npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-add-phase-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables stacking new research phases onto the end of the current milestone in a project roadmap, automating phase bookkeeping and state updates to keep planning consistent.

Core Features & Use Cases

  • Next phase creation: computes the next sequential phase number, slugifies the description, and creates the phase directory.
  • Roadmap and state updates: inserts the new phase into ROADMAP.md and updates STATE.md/state.json to reflect the addition.
  • Reproducible workflow: ensures consistent phase evolution within the GPD-driven research workflow for complex physics projects.

Quick Start

Invoke gpd-add-phase with a phase description to append a new phase to the current milestone.

Frequently Asked Questions about gpd-add-phase

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

FAQPage Schema
How do I add a new research phase to a roadmap automatically?

Automating roadmap phase creation involves computing the next sequential phase number, slugifying the description, creating the phase directory under .gpd/phases, and synchronizing ROADMAP.md and STATE.md via the gpd CLI.

How do I keep STATE.md and ROADMAP.md consistent when adding project phases?

STATE.md and ROADMAP.md stay consistent when adding project phases because the skill inserts the new phase into ROADMAP.md and updates STATE.md and state.json, synchronizing the roadmap state via the gpd CLI.

What is the GPD workflow for sequentially numbering research phases?

In the GPD workflow, sequentially numbering research phases involves automatically computing the next sequential phase number at the end of the current milestone, ensuring consistent phase evolution within GPD-driven projects.

Do I need the gpd CLI to create phase directories under .gpd/phases?

Creating phase directories under .gpd/phases requires the gpd CLI, which the skill uses to satisfy end-to-end workflow requirements including directory creation, slug generation, and roadmap state synchronization.

Can I automate phase bookkeeping for complex physics projects like tokamak research?

Automating phase bookkeeping for complex physics projects like tokamak research is supported by the skill, which ensures reproducible workflow and consistent phase evolution within the GPD-driven research workflow by automating directory creation and state updates.