gsd-insert-phase

To insert urgent work without renumbering phases, you can insert a decimal sub-phase like 72.1 after an existing integer phase. This preserves the original sequence and dependencies while accommodating the new task.

A decimal phase in milestone planning is a sub-phase, such as 74.2, inserted between existing integer phases. It allows urgent work to be added mid-milestone without disrupting the overall numbering sequence.

To add a new phase between existing milestones, specify the after-phase number and a description. The workflow validates the target phase exists, computes the correct decimal numbering, and updates the roadmap atomically.

Inserting a decimal phase preserves dependencies across the roadmap by avoiding cascading renumbering. The workflow updates the plan atomically, maintaining consistency across all generated artifacts and preserving the original sequence.

You need to provide an after-phase number and a description for the new phase. The workflow validates these inputs to ensure the target phase exists before computing the decimal numbering and updating the roadmap.

Use decimal phase insertion when urgent work emerges mid-milestone and you need to slot it between existing phases. This approach avoids the cascading renumbering of the entire roadmap, preserving sequence and dependencies.