gsd-insert-phase

Insert decimal-numbered phases into roadmap milestone sequences with validation.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill gsd-insert-phase-mint-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-insert-phase
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-insert-phase
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-insert-phase-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In project roadmaps, urgent work discovered mid-milestone often requires renumbering subsequent phases. This manual reordering is error-prone and disrupts planned timelines.

Core Features & Use Cases

  • Decimal-phase insertion: add a new phase with a decimal suffix (e.g., 72.1) between two existing phases to preserve order.
  • Validation & safety: verify the after-phase exists, ensure proper decimal numbering, and prevent conflicts.
  • Use Case: When phase 72 is planned and 73 is upcoming, insert 72.1 to accommodate urgent work without renumbering downstream phases.

Quick Start

Provide the after-phase number and a concise description to insert between phases.

Frequently Asked Questions about gsd-insert-phase

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

FAQPage Schema
How do I insert an urgent phase into a project roadmap without renumbering subsequent phases?

To insert an urgent phase into a project roadmap without renumbering subsequent phases, use decimal numbering to slot the new task between two consecutive milestones, such as adding phase 72.1 between phases 72 and 73.

What is decimal phase numbering in project management and when is it needed?

Decimal phase numbering in project management assigns decimal suffixes like 72.1 to new phases, and it is needed when urgent work is discovered mid-milestone and must be sequenced without disrupting planned downstream timelines.

What inputs do I need to add a decimal phase to an existing milestone sequence?

To add a decimal phase to an existing milestone sequence, you need to provide the after-phase number where the insertion occurs and a concise description of the urgent task to update the roadmap state accordingly.

Can the roadmap insertion process validate if my target phase number exists?

Yes, the roadmap insertion process validates the target phase by verifying the after-phase exists, ensuring proper decimal numbering calculation, and preventing numbering conflicts to maintain roadmap safety.

What happens if I insert a decimal phase between two consecutive roadmap phases?

When you insert a decimal phase between two consecutive roadmap phases, the system calculates the correct decimal suffix, validates the target phase, and updates the roadmap state to preserve the existing milestone order.