gsd-insert-phase

Insert urgent tasks as decimal phases into a roadmap without renumbering existing phases.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/zerAda/RestaurantAgentAutomation --skill gsd-insert-phase-zerada
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-insert-phase
Source: https://github.com/zerAda/RestaurantAgentAutomation/tree/main/.agent/skills/gsd-insert-phase
Command: npx skills add https://github.com/zerAda/RestaurantAgentAutomation --skill gsd-insert-phase-zerada

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the challenge of adding urgent tasks to a roadmap without disrupting the existing phase numbering.

Core Features & Use Cases

  • Decimal Phase Insertion: Insert urgent work as decimal phases (e.g., 72.1, 72.2) to maintain roadmap sequence.
  • Preservation of Logic: Ensures that urgent tasks are integrated logically without renumbering phases.
  • Use Case: For instance, if an urgent task needs to be inserted into a milestone, you can use this Skill to add it as 72.1, maintaining the logical order.

Quick Start

Insert an urgent task as decimal phase 72.1 with description "Urgent task update".

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 tasks into a roadmap without renumbering existing phases?

Decimal phase insertion works by assigning urgent tasks a decimal number like 72.1 within an existing milestone. This mechanism maintains the logical order of your roadmap without altering the original phase numbering sequence.

What is the best way to add urgent work to a project management roadmap without disrupting the sequence?

The best way to add urgent work without disrupting your project management roadmap sequence is using decimal phase insertion. It integrates urgent tasks as decimal phases, ensuring logical order and phase preservation without renumbering existing items.

When do I need to use decimal phases for urgent tasks in project management?

You need to use decimal phases for urgent tasks when an urgent task requires insertion into an existing milestone. This approach maintains logical order and phase numbering without forcing a full renumbering of your project management roadmap.

Does adding decimal phases to a roadmap preserve the original phase numbering?

Yes, adding decimal phases to a roadmap preserves the original phase numbering. The process inserts urgent tasks as decimal phases, such as 72.1, ensuring the existing phases remain unchanged while maintaining logical sequence order.

Can I insert multiple urgent tasks into a single roadmap milestone?

Yes, you can insert multiple urgent tasks into a single roadmap milestone by using sequential decimal phases like 72.1 and 72.2. This maintains logical order and keeps the original phase numbering fully intact.