gsd-phase

Manage CRUD operations for ROADMAP.md phases with consistent numbering.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-phase
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-phase
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the overhead and mistakes involved in manually editing ROADMAP.md phases, ensuring phase numbering and updates stay consistent as your roadmap changes.

Core Features & Use Cases

  • Add phases to the end of a milestone: Appends a new integer phase when you’re expanding planned work.
  • Insert urgent decimal phases: Places time-sensitive work (e.g., 72.1) between existing phases for better sequencing.
  • Remove and renumber future phases: Deletes a future phase and updates subsequent numbering to maintain order.
  • Edit phase fields in place: Updates any phase attribute without restructuring the surrounding timeline.

Use Case: You realize that after phase 72 you need an urgent sub-task before phase 73—insert it as 72.1, then later remove a phase that is no longer needed while keeping the numbering correct.

Quick Start

Run the command with the appropriate flag and arguments to add, insert, remove, or edit a phase in ROADMAP.md in the correct workflow mode.

Frequently Asked Questions about gsd-phase

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

FAQPage Schema
How do I manage roadmap phases in a markdown file without breaking the milestone structure?

Managing roadmap phases in a markdown file without breaking milestones requires CRUD operations that preserve structure and maintain consistent numbering. This Skill automates phase additions, removals, and edits while keeping the surrounding timeline intact.

How do I insert an urgent decimal phase between existing roadmap items?

To insert an urgent decimal phase between existing roadmap items, use the insert operation to place time-sensitive work like phase 72.1 between sequential phases. This ensures proper decimal sequencing without rewriting the entire roadmap.

Can I remove a future phase and automatically renumber the remaining phases?

Yes, you can remove a future phase and automatically renumber subsequent phases. The removal operation deletes the target entry and updates the numbering of all following phases to maintain correct sequential order in the roadmap.

What is the best way to update phase fields in a roadmap without restructuring the timeline?

The best way to update phase fields in a roadmap without restructuring the timeline is using an in-place edit operation. This modifies specific phase attributes directly while leaving the surrounding milestone structure and numbering unchanged.

Do I need specific workflow routing to add a new phase to the end of a milestone?

Yes, adding a new phase to the end of a milestone requires routing by a leading flag in your arguments. This delegates execution to the corresponding workflow with validation gates enforced to ensure the append operation is safe.

Does this roadmap phase management approach require external dependencies or components?

No, this roadmap phase management approach requires no external dependencies or components. It operates standalone using YAML frontmatter and markdown routing flags to execute phase CRUD operations directly within the roadmap file.