Insert a decimal phase between existing roadmap phases without renumbering.
npx skills add https://github.com/thecomputer07/qsd --skill qsd-insert-phase
Please help me install this Agent Skill. Skill: qsd-insert-phase Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-insert-phase Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-insert-phase
Insert urgent work as decimal phase (e.g., 72.1) between existing phases to preserve the planned sequence without renumbering. This skill enables teams to slot urgent tasks into a milestone roadmap by using decimal phase numbering (e.g., 72.1, 72.2), ensuring continuity and minimal disruption to planning.
Invoke the insert-phase workflow to insert a new decimal phase after the specified phase and update the roadmap accordingly.
High-intent search queries and answers about installing and using this skill.
To add urgent work without renumbering phases, you can insert a decimal phase (e.g., 72.1) between existing milestones. This places the new phase after a specified target while preserving the overall planned sequence.
Decimal phase insertion is a roadmap planning technique that slots urgent tasks between existing milestones using decimal numbering. It maintains continuity and ensures minimal disruption by calculating decimal values rather than shifting subsequent phase numbers.
To insert a decimal phase, invoke the insertion workflow after the specified target phase. The process parses arguments, verifies the target phase exists, calculates the decimal number, and updates the roadmap state to safely accommodate the new entry.
Yes, the decimal phase insertion process enforces validation gates before updating. It verifies that the target phase exists, prevents invalid decimal numbers, and ensures safe, idempotent updates to the milestone sequence within the workflow.
No, the roadmap must be resolvable in-workflow to insert decimal phases. The insertion process requires this environment to validate the target phase, calculate the decimal number, and execute safe state updates.
Use decimal phase numbering for mid-milestone adjustments when urgent work arises and renumbering would disrupt the planned sequence. This approach preserves continuity by placing tasks like phase 72.1 between existing milestones.
dobrinz123Insert decimal phases into milestone-based GSD roadmaps without renumbering.
nnexaiInsert urgent work items as decimal-numbered phases into a project roadmap.
thecomputer07Automate adding a new phase to the current milestone in a roadmap.
rkz91Insert a decimal phase into a milestone roadmap and update downstream references.
