gsd-insert-phase

Inserts an urgent decimal phase into an existing milestone roadmap.

Updated Apr 22, 2026

Search Tags:#automation #workflow #planning #roadmap #milestone #decimal-phase #insert-phase

Ready to run

npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-insert-phase-hadpadrahul

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-insert-phase
Source: https://github.com/hadpadrahul/school-erp/tree/main/.codex/skills/gsd-insert-phase
Command: npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-insert-phase-hadpadrahul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inserting urgent work into the correct place in an existing milestone roadmap by inserting a decimal phase without renumbering later phases.

Core Features & Use Cases

Decimal-based phase insertion to preserve sequence (e.g., 72.1) after an identified phase.
Validates inputs, updates roadmap, and maintains consistency of phase numbering.
Use Case: mid-milestone discovery of urgent tasks requires a minimal disruption to planning, with automatic recalculations.

Quick Start

Instruct the tool to insert a new urgent task after phase 72 with description Fix login bug and set it as 72.1.

Frequently Asked Questions about gsd-insert-phase

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

FAQPage Schema

How do I add an urgent phase to a roadmap without renumbering subsequent milestones?▼

To add an urgent phase without renumbering subsequent milestones, insert a decimal phase like 72.1 after the identified phase. This preserves the original sequence while accommodating urgent tasks discovered mid-milestone.

What is decimal phase insertion in project planning?▼

Decimal phase insertion is a milestone management technique that adds urgent work as a decimal number, such as phase 72.1, ensuring sequence consistency without forcing a complete roadmap renumbering.

When do I need to use decimal numbering for milestone management?▼

You need decimal numbering for milestone management when urgent work is discovered mid-milestone. It allows minimal disruption to planning by inserting a decimal-ordered phase directly after an existing phase.

How do I validate arguments and calculate decimals when inserting a roadmap phase?▼

The insertion workflow automatically validates arguments, calculates the correct decimal value, and updates the roadmap to maintain phase numbering consistency during the urgent task insertion process.

Can I insert multiple urgent tasks into the same milestone phase?▼

Yes, you can insert multiple urgent tasks into the same phase by applying decimal calculation logic. The workflow validates inputs and updates the roadmap to maintain sequence consistency for each new insertion.

What are the limitations of using decimal phases for urgent roadmap updates?▼

Decimal phase insertion avoids renumbering later phases but requires strict argument validation. If the workflow encounters invalid inputs or phase conflicts, the roadmap update may fail to maintain sequence consistency.