gsd-insert-phase

To insert urgent tasks without renumbering phases, add the unplanned work as a decimal-numbered phase, such as 72.1, between existing integer phases in your milestone roadmap. This preserves the original sequence while accommodating urgent mid-milestone tasks.

Decimal phase insertion in milestone planning is a method of adding urgent mid-milestone work as decimal-numbered phases, like 72.1, between existing integer phases. This technique maintains logical workflow order without requiring a full renumbering of the project roadmap.

You should use a decimal phase instead of renumbering when an unplanned urgent task, such as a critical bug fix, is discovered during active milestone execution and must be completed before proceeding to the next scheduled integer phase.

Yes, you can add a critical bug fix to an active project workflow by inserting it as a decimal phase between existing integer phases. This approach preserves roadmap integrity by avoiding the need to renumber subsequent scheduled phases.

The best way to handle unplanned urgent tasks during active milestone execution is to insert them as decimal-numbered phases between existing integer phases. This accommodates the urgent work while preserving the logical phase ordering of the milestone roadmap.