gsd-insert-phase

Insert urgent work by adding a decimal phase between existing phases, such as 72.1, to preserve sequencing and avoid renumbering the entire roadmap. This approach slots mid-milestone tasks directly after a specified phase while keeping the original order intact.

A decimal phase is a fractional milestone number used when you need to insert urgent work discovered mid-milestone without disrupting existing numbering. It preserves logical order by slotting tasks between planned phases rather than shifting subsequent milestones.

Add a mid-milestone task by providing the target after-phase number and a description. The workflow validates the target phase, calculates the correct decimal increment, and updates the roadmap state accordingly to slot the new item in.

Decimal-phase insertion enforces argument parsing and target phase validation before updating the roadmap. It applies clear failure handling to prevent invalid phase numbers or unsafe roadmap updates from corrupting your milestone sequence.

Yes, decimal-phase insertion supports descriptive task details to track urgent work within the ongoing plan. You provide a description alongside the phase number to ensure the inserted item is documented within the existing roadmap state.

The best way to manage urgent work mid-milestone is inserting decimal phases to slot tasks after a specified phase. This approach computes the correct increment and updates the plan, avoiding full roadmap renumbering while preserving sequence integrity.