gsd-insert-phase

Insert decimal phases into milestone-based GSD roadmaps without renumbering.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-insert-phase-dobrinz123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-insert-phase
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-insert-phase
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-insert-phase-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Insert urgent, mid-milestone work into an existing roadmap without renumbering integer phases, preserving sequence and project context while accommodating ad-hoc tasks discovered during execution.

Core Features & Use Cases

  • Decimal Phase Insertion: Compute and assign decimal phase numbers (e.g., 72.1) to place urgent tasks between existing phases.
  • Validation & Safety Gates: Parse arguments, verify the target phase exists, and ensure roadmap integrity before applying updates.
  • Seamless Roadmap Updates: Update project state and persist changes in the workflow so that planning and execution tools continue to operate consistently.
  • Use Case: Add a hotfix or discovery task into an ongoing milestone between planned phases without shifting all downstream numbering.

Quick Start

Insert a decimal phase after phase 72 with the description Fix critical payment bug discovered in production.

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 urgent tasks into a project roadmap without renumbering existing phases?

Insert a decimal phase into your roadmap to place urgent tasks between existing integer phases. This approach computes and assigns decimal phase numbers, allowing you to add hotfixes or discovery tasks without shifting all downstream milestone numbering.

What is a decimal phase in milestone-based task management?

A decimal phase in milestone-based task management is an intermediate phase number, such as 72.1, inserted between existing integer phases. It accommodates urgent ad-hoc work discovered during execution without renumbering downstream milestones.

How do I add a hotfix to an ongoing milestone between planned phases?

Insert a decimal phase after the target integer phase within your workflow. The system parses arguments, verifies the target phase exists, calculates the decimal number, and updates the roadmap while preserving validation gates and workflow state.

Does inserting a decimal phase preserve validation gates and workflow state?

Yes, inserting a decimal phase preserves validation gates and workflow state. The process performs argument parsing and phase verification to ensure roadmap integrity before applying updates, so planning and execution tools continue to operate consistently.

Can I use decimal phase insertion for any task management workflow?

Decimal phase insertion applies specifically to milestone-based GSD workflows. It is designed for project roadmaps where urgent tasks must be scheduled between planned phases without renumbering, rather than for all task management approaches.

What are the limitations of decimal phase insertion for roadmap updates?

A limitation of decimal phase insertion is that it requires an existing target integer phase for verification. If the roadmap lacks milestone-based phases, the decimal calculation and insertion cannot place urgent work between planned phases correctly.