gsd-insert-phase

To insert urgent phases without renumbering, use decimal numbering to add intermediate phases like 72.1 between existing integer milestones. This preserves the original phase sequence while accommodating newly discovered mid-execution work.

Decimal phase sequencing assigns numbers like 72.1 or 72.2 to urgent phases inserted between existing integer phases during execution. It maintains roadmap ordering and validation consistency without forcing a full renumber of downstream milestones.

You need decimal numbering for milestone planning when urgent work is discovered mid-execution and must be sequenced between already-defined integer phases. This avoids disrupting the existing roadmap structure while fitting the new phase into the correct position.

Yes, inserting a decimal-numbered phase preserves validation gates like phase verification and decimal calculation consistency. The workflow runs end-to-end to ensure the roadmap update maintains argument parsing and state validation integrity.

The best way to sequence newly discovered work is running an insert-phase workflow that calculates a decimal phase number based on the preceding integer phase. This ensures the urgent work is ordered correctly without renumbering subsequent phases.

You need to provide an after-phase number indicating where the new phase should be inserted, along with a short description of the urgent work. The workflow uses these inputs to calculate the decimal number and update the roadmap state.