gsd-insert-phase

Insert urgent work into a roadmap without renumbering by using decimal phase numbering, placing newly discovered tasks between existing integer phases like 72.1 or 72.2. This preserves original milestone sequences and keeps delivery plans stable.

Decimal phase numbering is a roadmap management technique that assigns values like 72.1 to urgent tasks inserted between existing integer phases. It makes room for mid-milestone surprises during active delivery while preserving validation gates and roadmap continuity.

You can add a milestone between existing phases during active delivery by applying decimal phase calculation. The process verifies the target phase, calculates the correct decimal step, and updates roadmap state with guardrails intact to ensure validation-aware execution.

Maintain roadmap state with validation gates by running phase verification before inserting urgent work. The insertion process calculates the correct decimal step and applies state updates with guardrails intact, ensuring validation-aware execution throughout the workflow.

Decimal phase insertion applies specifically to milestone-based execution workflows where newly discovered tasks must be placed between integer phases. It requires argument parsing and phase verification to insert urgent work without disrupting planned milestones.

Avoid inserting urgent work into a phase roadmap when the active delivery workflow is not milestone-based or lacks clear integer phases. This decimal insertion approach requires existing phase verification and validation gates to properly update roadmap state.