gsd-insert-phase

You can insert urgent tasks into a project roadmap by adding decimal-numbered phases, such as 72.1, between integer phases. This accommodates urgent work while preserving sequence and historical integrity without shifting the entire roadmap.

Decimal phase insertion is a project management technique that adds phases like 72.1 or 72.2 between integer milestones. It allows teams to slot urgent mid-milestone work, such as critical bugs or compliance tasks, into the workflow without renumbering established phases.

To add a critical bug fix to an active milestone roadmap, invoke decimal phase insertion with a target phase number and description. The system validates arguments, verifies the target phase exists, calculates the next available decimal slot, and updates the roadmap atomically.

Use decimal phases when urgent work is discovered mid-milestone and you need to preserve sequence and historical integrity. Renumbering shifts the entire roadmap, whereas decimal insertion slots urgent tasks between integer phases while maintaining audit logs and state.

Yes, decimal phase insertion updates the roadmap atomically and preserves audit logs and state via the configured workflow. This ensures historical integrity is maintained even when urgent mid-milestone tasks are added between existing integer phases.

Yes, decimal phase insertion applies to get-shit-done workflows where multiple urgent tasks arise. It calculates the next available decimal slot sequentially, allowing you to add phases like 72.1 and 72.2 after a target phase to accommodate several urgent items.