gsd-insert-phase

To insert urgent work into a project roadmap without re-sequencing, you can assign the new task a decimal phase number between existing integer phases. This maintains the logical flow while accommodating agile adjustments.

Decimal phase insertion in agile project planning creates sub-phases like 72.1 for urgent tasks. It allows mid-milestone adjustments by slotting critical work between existing integer-numbered roadmap phases.

You can add a critical bug fix to an active roadmap by inserting it as a decimal-numbered phase. If the bug occurs during phase 72, the fix becomes phase 72.1, leaving the original phase 73 intact.

Yes, you can adjust a project roadmap for unforeseen urgent tasks without disrupting the planned sequence by using decimal phase insertion. This approach updates the roadmap state while keeping the original milestones intact.

The best way to handle mid-milestone adjustments in task management is decimal phase insertion. It bypasses full re-planning by verifying the current phase and calculating a decimal number to insert the urgent work.

A limitation of inserting urgent tasks as decimal phases is the reliance on argument parsing and phase verification logic. Heavy insertion of urgent work may require eventual full re-sequencing to maintain roadmap readability.