gsd-insert-phase

To insert an urgent task without renumbering a milestone roadmap, add a decimal phase between two consecutive integer phases. This preserves the logical sequence for stakeholders while accommodating new work discovered mid-milestone.

A decimal phase in project planning is a fractional milestone number, like 72.1, inserted between adjacent integer phases. It accommodates urgent work discovered mid-milestone while maintaining the correct chronological ordering of the roadmap.

You add a new phase between integer milestones by instructing the system to insert a decimal phase immediately after a specified integer. It validates the target phase number, calculates the decimal value, and updates the roadmap state.

You need decimal numbering for roadmap phases when urgent work appears mid-milestone and must be slotted between existing phases. This prevents the need to renumber subsequent tasks, ensuring traceability and consistency across the project plan.

Yes, inserting a decimal phase validates the target after-phase number. It applies robust parsing and decimal calculation to ensure the updated roadmap state maintains logical sequence and traceability for all project stakeholders.

The best way to maintain roadmap ordering when urgent work is discovered is inserting a decimal phase between consecutive integers. This approach applies input validation and state updates, bypassing the need to renumber subsequent phases.