gsd-insert-phase

Insert urgent work as decimal phases into project roadmaps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/aydadevelop/turborepo-starter --skill gsd-insert-phase-aydadevelop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-insert-phase
Source: https://github.com/aydadevelop/turborepo-starter/tree/main/.github/skills/gsd-insert-phase
Command: npx skills add https://github.com/aydadevelop/turborepo-starter --skill gsd-insert-phase-aydadevelop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of incorporating urgent tasks into an existing project roadmap without disrupting the planned sequence of milestones.

Core Features & Use Cases

  • Dynamic Phase Insertion: Allows for the insertion of new work items as decimal phases (e.g., 72.1) between existing integer phases.
  • Roadmap Preservation: Maintains the logical flow of the original roadmap while accommodating unforeseen urgent tasks.
  • Use Case: A critical bug is discovered during sprint 72. This Skill can insert the bug fix as phase 72.1, ensuring it's addressed promptly without renumbering subsequent planned phases like 73, 74, etc.

Quick Start

Insert urgent work as phase 72.1 with the description "Fix critical login bug".

Frequently Asked Questions about gsd-insert-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I insert urgent work into a project roadmap without disrupting existing milestones?▼

Insert urgent work into a project roadmap by assigning it a decimal phase identifier, such as 72.1, between existing integer phases. This preserves the logical sequence of planned milestones while accommodating unforeseen tasks.

What is decimal phase insertion in agile project planning?▼

Decimal phase insertion is a task management technique that adds urgent work as decimal phases, like 72.1 or 72.2, between established integer roadmap milestones, ensuring critical tasks are addressed without renumbering subsequent planned phases.

How do I add a critical bug fix to a sprint roadmap without renumbering phases?▼

Add a critical bug fix to a sprint roadmap by inserting it as a decimal phase, such as 72.1, immediately following the current integer phase. This maintains the original numbering of future planned phases like 73 and 74.

Can I insert multiple urgent tasks into the same project phase?▼

Yes, you can insert multiple urgent tasks into the same project phase by assigning them sequential decimal identifiers, such as 72.1 and 72.2, ensuring each mid-milestone task is tracked logically within the workflow.

Does this phase insertion approach support agile workflow validation and roadmap updates?▼

Yes, the phase insertion approach supports agile workflow validation and roadmap updates through an end-to-end process that calculates decimal identifiers and preserves the logical flow of the existing project roadmap.

When should I use decimal phase insertion instead of reordering my entire project roadmap?▼

Use decimal phase insertion when mid-milestone urgent tasks arise and you need to address them promptly without disrupting the planned sequence, avoiding the need to reorder or renumber subsequent integer phases in your project roadmap.