gsd-phase

Manage CRUD operations for phases in ROADMAP.md with flag-based routing.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-phase-tinner-deinno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-phase
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-phase
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-phase-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual, error-prone work of adding, inserting, removing, or editing ROADMAP phases by updating the milestone phase list consistently with the correct numbering rules.

Core Features & Use Cases

  • Single-command phase CRUD: Add a new integer phase at the end of the current milestone, insert urgent decimal phases between existing ones, remove future phases and renumber the rest, or edit phase fields in place.
  • Flag-based routing: Uses --insert, --remove, and --edit to select the correct workflow without requiring separate skill calls.
  • Roadmap-aware validation: Loads and resolves the roadmap and state inside the target workflow to preserve the same validation gates for each operation.

Use case: While planning a delivery, you discover urgent work that must land between two scheduled phases; you insert it as a decimal phase (e.g., 72.1) and keep subsequent numbering aligned.

Quick Start

Run gsd-phase to add the next phase for your current milestone using your provided phase description.

Frequently Asked Questions about gsd-phase

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

FAQPage Schema
How do I insert a new phase between existing roadmap milestones without breaking the numbering?

To insert roadmap phases without breaking numbering, use a decimal value like 72.1 to place urgent work between scheduled milestones. The workflow parses the ROADMAP.md file and validates the update to keep subsequent phase ordering aligned automatically.

What is the best way to remove a future milestone phase and renumber the rest of the roadmap?

Removing future roadmap phases and renumbering the rest is handled through a single remove command. The workflow loads your roadmap state, deletes the specified phase, and automatically renumbers subsequent milestones to preserve correct sequential ordering.

Can I edit an existing phase description in place directly within ROADMAP.md?

Yes, you can edit existing roadmap phase fields in place without breaking milestone ordering. Routing the command with an edit flag triggers workflow-managed parsing and validation to ensure correct roadmap state updates directly inside your ROADMAP.md file.

How do I add a new integer phase to the current milestone in my roadmap planning?

Adding a new integer roadmap phase to the current milestone requires running the default command with your phase description. The workflow appends the new phase at the end of the current milestone list while applying roadmap-aware validation gates.

Do I need separate commands for adding, inserting, and editing phases during project planning?

No, separate commands are not needed for phase CRUD operations. An optional leading flag such as insert, remove, or edit routes the single command to the correct workflow, managing parsing and validation without requiring multiple skill calls.

Why does inserting a decimal phase like 72.1 help with urgent project scheduling updates?

Inserting a decimal phase like 72.1 helps with urgent project scheduling by slotting new work between existing roadmap milestones without altering their original integer numbering. This keeps your overall delivery sequence intact while accommodating immediate priorities.