gsd-phase

Add, insert, remove, or edit ROADMAP.md phase entries with consistent numbering.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-phase-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-phase
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-phase
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-phase-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents messy, error-prone manual edits to ROADMAP.md phase numbering by providing a single command that can add, insert, remove, or edit phases while keeping the numbering consistent.

Core Features & Use Cases

  • Add phases (default): Appends a new integer phase to the end of the current milestone.
  • Insert urgent work (--insert): Inserts a decimal phase (e.g., 72.1) at the correct position between existing phases.
  • Remove and renumber (--remove): Deletes a future phase and renumbers subsequent phases to keep ordering valid.
  • Edit in place (--edit): Modifies any field of an existing phase without rewriting the whole roadmap section.

Quick Start

Run gsd-phase to add a new phase description to the end of the current milestone, or use the --insert or --remove flags to surgically adjust phase ordering.

Frequently Asked Questions about gsd-phase

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

FAQPage Schema
How do I keep ROADMAP.md phase numbering consistent when adding or removing phases?

To keep phase numbering consistent in ROADMAP.md, use an automated phase management command that appends, inserts, removes, or edits phase entries while automatically validating and renumbering subsequent phases to maintain valid ordering.

What is the best way to insert an urgent task between existing project phases in a roadmap?

The best way to insert urgent work between existing roadmap phases is to use an insert flag that creates a decimal phase, such as 72.1, positioning the new entry correctly without disrupting the overall sequence.

How do I remove a future phase from a milestone and renumber the remaining phases?

To remove a future phase and renumber remaining phases, execute a remove command that deletes the targeted phase entry and automatically renumbers subsequent phases to ensure the milestone ordering remains valid.

Can I edit a specific field of an existing phase without rewriting the entire roadmap section?

Yes, you can edit a specific field of an existing phase without rewriting the entire roadmap section by using an in-place edit command that modifies only the targeted phase entry while preserving the surrounding structure.

Do I need a specific ROADMAP state format before running phase management operations?

Yes, phase management operations require a valid ROADMAP state to resolve phase validation in-workflow, ensuring that add, insert, remove, and edit commands execute reliably against correctly structured milestone data.