kata-insert-phase

Insert a decimal phase between existing roadmap phases without renumbering.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/gannonh/kata-marketplace --skill kata-insert-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kata-insert-phase
Source: https://github.com/gannonh/kata-marketplace/tree/main/plugins/kata/skills/kata-insert-phase
Command: npx skills add https://github.com/gannonh/kata-marketplace --skill kata-insert-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables urgent decimal-phase insertions into a milestone roadmap, allowing you to add mid-milestone work without renumbering existing phases.

Core Features & Use Cases

  • Compute the next decimal phase after a target phase and generate a slug for the new phase
  • Create the phase directory under .planning/phases/pending
  • Update ROADMAP.md and STATE.md to reflect the inserted phase
  • Suitable for urgent bug fixes or scope changes discovered mid-milestone

Quick Start

Use the kata-insert-phase command to insert a new decimal phase after a specified phase, e.g. /kata-insert-phase 72 Fix critical auth bug

Frequently Asked Questions about kata-insert-phase

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

FAQPage Schema
How do I add an urgent task to an agile roadmap without renumbering existing milestones?

You can insert an urgent decimal phase between existing milestones without renumbering the roadmap. The process computes the next decimal value after a target phase, creates a pending directory, and updates ROADMAP.md and STATE.md to preserve the original phase order.

What is a decimal phase in agile roadmap planning?

A decimal phase in roadmap planning is an intermediate step, like 72.1, inserted between existing milestones. It allows teams to schedule urgent bug fixes or scope changes immediately without disrupting the sequential numbering of planned phases.

How do I insert a mid-milestone scope change into a pending phase directory?

To insert a mid-milestone scope change, specify the target phase number and a description. The tool parses the target phase, computes the next decimal, generates a descriptive slug, and creates the new phase directory under .planning/phases/pending.

Can I update ROADMAP.md and STATE.md automatically when scheduling urgent agile work?

Yes, inserting a decimal phase automatically updates both ROADMAP.md and STATE.md to reflect the newly inserted urgent work. This ensures your roadmap and project state files remain synchronized without manual editing when mid-milestone tasks arise.

What is the best way to handle urgent bug fixes discovered mid-milestone in a structured roadmap?

The best approach is inserting a decimal phase for the urgent bug fix after the current milestone. This preserves existing roadmap order, generates a descriptive slug for the fix, and schedules the work immediately without renumbering subsequent planned phases.