gsd-insert-phase

Insert urgent work as decimal phases between existing roadmap phases.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/jjchambers80/judgesdirectory --skill gsd-insert-phase-jjchambers80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-insert-phase
Source: https://github.com/jjchambers80/judgesdirectory/tree/main/.github/skills/gsd-insert-phase
Command: npx skills add https://github.com/jjchambers80/judgesdirectory --skill gsd-insert-phase-jjchambers80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Urgent work discovered mid-milestone often forces teams to renumber an entire roadmap or awkwardly append tasks at the end. This Skill inserts urgent work as a decimal phase (e.g., 72.1) between existing integer phases, preserving the planned sequence without renumbering. ## Core Features & Use Cases - Decimal Phase Insertion: Adds urgent work as a decimal-numbered phase (72.1, 72.2) directly after a specified integer phase. - Roadmap Preservation: Keeps the logical order of planned phases intact while accommodating mid-milestone insertions. - Validation Gates: Enforces argument parsing, phase verification, decimal calculation, and roadmap updates through the insert-phase workflow. - Use Case: During execution of phase 72, a critical security fix is discovered. Run the insertion to create phase 72.1 for the fix, then continue with phase 73 as originally planned. ## Quick Start Ask the assistant to insert a new phase after phase 72 with a short description of the urgent work, for example: insert phase after 72 for the critical auth fix.

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 task between existing roadmap phases?▼

Provide the phase number to insert after and a description of the urgent work. The workflow creates a decimal phase such as 72.1 after phase 72, preserving the numbering of all existing phases.

What is decimal phase numbering in roadmap planning?▼

Decimal phase numbering assigns inserted work values like 72.1 or 72.2 between integer phases. It keeps the original roadmap sequence intact while accommodating urgent tasks discovered during execution.

Can I insert multiple phases after the same integer phase?▼

Yes, multiple insertions after the same phase produce sequential decimals such as 72.1, 72.2, and so on. The workflow calculates the next available decimal value automatically.

What happens if the target phase number does not exist?▼

The workflow includes phase verification as a validation gate. If the specified phase cannot be found in the roadmap, the insertion fails validation rather than corrupting the roadmap state.

When should I avoid inserting decimal phases?▼

Avoid decimal insertions when the new work is large enough to warrant replanning the milestone, or when too many inserted phases make the roadmap hard to follow. In those cases, restructure the roadmap instead.