gpd-insert-phase

Inserting an urgent decimal phase (N.M) between existing milestones preserves roadmap integrity without renumbering. The tool calculates the correct decimal position, verifies the target phase, and updates ROADMAP.md and STATE.md to reflect the new insertion.

A decimal phase is needed during mid-project discoveries requiring immediate tracking, such as new analyses or reviewers' concerns. It captures urgent work between established milestones while maintaining the original numbering sequence of your roadmap.

The best way to track urgent mid-project work is decimal-phase insertion, which adds an N.M phase between existing milestones. This approach synchronizes ROADMAP.md and STATE.md automatically while maintaining an auditable history of the change.

To calculate the correct decimal number for a roadmap insertion, the tool verifies the target after-phase and applies decimal calculation logic. This ensures the new urgent phase is positioned accurately within the existing milestone sequence.

Yes, you can maintain an auditable history when adding urgent tasks. The insertion process records the decision and creates an auditable insertion record, ensuring full traceability of mid-project changes within your roadmap documentation.

Yes, inserting a new decimal phase automatically updates both ROADMAP.md and STATE.md files. This roadmap and state synchronization ensures your project tracking documents reflect the urgent insertion immediately without manual file edits.