--- name: insert-phase description: Use this skill when inserting urgent work as a decimal phase between existing phases, adding mid-milestone work, or creating intermediate phases. Triggers include "insert phase", "add urgent phase", "create decimal phase", "insert between phases", and "urgent work". metadata: version: "0.1.0" user-invocable: true disable-model-invocation: false allowed-tools: - Read - Write - Bash --- Insert a decimal phase for urgent work discovered mid-milestone that must be completed between existing integer phases. Uses decimal numbering (72.1, 72.2, etc.) to preserve the logical sequence of planned phases while accommodating urgent insertions. Purpose: Handle urgent work discovered during execution without renumbering entire roadmap. <\/objective> @.planning\/ROADMAP.md @.planning\/STATE.md <\/execution_context> Parse the command arguments: - First argument: integer phase number to insert after - Remaining arguments: phase description Example: `\/kata:insert-phase 72 Fix critical auth bug` → after = 72 → description = "Fix critical auth bug" Validation: ```bash if [ $# -lt 2 ]; then echo "ERROR: Both phase number and description required" echo "Usage: \/kata:insert-phase " echo "Example: \/kata:insert-phase 72 Fix critical auth bug" exit 1 fi ``` Parse first argument as integer: ```bash after_phase=$1 shift description="$*" # Validate after_phase is an integer if ! [[ "$after_phase" =~ ^[0-9]+$ ]]; then echo "ERROR: Phase number must be an integer" exit 1 fi ``` <\/step> Load the roadmap file: ```bash if [ -f .planning\/ROADMAP.md ]; then ROADMAP=".planning\/ROADMAP.md" else echo "ERROR: No roadmap found (.planning\/ROADMAP.md)" exit 1 fi ``` Read roadmap content for parsing. <\/step> Verify that the target phase exists in the roadmap: 1. Search for "### Phase {after_phase}:" heading 2. If not found: ``` ERROR: Phase {after_phase} not found in roadmap Available phases: [list phase numbers] ``` Exit. 3. Verify phase is in current milestone (not completed\/archived) <\/step> Find existing decimal phases after the target phase: 1. Search for all "### Phase {after_phase}.N:" headings 2. Extract decimal suffixes (e.g., for Phase 72: find 72.1, 72.2, 72.3) 3. Find the highest decimal suffix 4. Calculate next decimal: max + 1 Examples: - Phase 72 with no decimals → next is 72.1 - Phase 72 with 72.1 → next is 72.2 - Phase 72 with 72.1, 72.2 → next is 72.3 Store as: `decimal_phase="$(printf "%02d" $after_phase).${next_decimal}"` <\/step> Convert the phase description to a kebab-case slug: ```bash slug=$(echo "$description" | tr '[:upper:]' '[:lower:]' | sed 's\/[^a-z0-9]\/-\/g' | sed 's\/--*\/-\/g' | sed 's\/^-\/\/;s\/-$\/\/') ``` Phase directory name: `{decimal-phase}-{slug}` Example: `06.1-fix-critical-auth-bug` (phase 6 insertion) <\/step> Create the phase directory structure: ```bash phase_dir=".planning\/phases\/${decimal_phase}-${slug}" mkdir -p "$phase_dir" ``` Confirm: "Created directory: $phase_dir" <\/step> Insert the new phase entry into the roadmap: 1. Find insertion point: immediately after Phase {after_phase}'s content (before next phase heading or "---") 2. Insert new phase heading with (INSERTED) marker: ``` ### Phase {decimal_phase}: {Description} (INSERTED) **Goal:** [Urgent work - to be planned] **Depends on:** Phase {after_phase} **Plans:** 0 plans Plans: - [ ] TBD (run \/kata:plan-phase {decimal_phase} to break down) **Details:** [To be added during planning] ``` 3. Write updated roadmap back to file The "(INSERTED)" marker helps identify decimal phases as urgent insertions. Preserve all other content exactly (formatting, spacing, other phases). <\/step> Update STATE.md to reflect the inserted phase: 1. Read `.planning\/STATE.md` 2. Under "## Accumulated Context" → "### Roadmap Evolution" add entry: ``` - Phase {decimal_phase} inserted after Phase {after_phase}: {description} (URGENT) ``` If "Roadmap Evolution" section doesn't exist, create it. Add note about insertion reason if appropriate. <\/step> Present completion summary: ``` Phase {decimal_phase} inserted after Phase {after_phase}: - Description: {description} - Directory: .planning\/phases\/{decimal-phase}-{slug}\/ - Status: Not planned yet - Marker: (INSERTED) - indicates urgent work Roadmap updated: {roadmap-path} Project state updated: .planning\/STATE.md --- ## ▶ Next Up **Phase {decimal_phase}: {description}** — urgent insertion `\/kata:plan-phase {decimal_phase}` _{`\/clear` first → fresh context window<\/sub>

---

**Also available:**
- Review insertion impact: Check if Phase {next_integer} dependencies still make sense
- Review roadmap

---
```
<\/step>

<\/process>

- Don't use this for planned work at end of milestone (use \/kata:add-phase)
- Don't insert before Phase 1 (decimal 0.1 makes no sense)
- Don't renumber existing phases
- Don't modify the target phase content
- Don't create plans yet (that's \/kata:plan-phase)
- Don't commit changes (user decides when to commit)
<\/anti_patterns>

Phase insertion is complete when:

- [ ] Phase directory created: `.planning\/phases\/{N.M}-{slug}\/`
- [ ] Roadmap updated with new phase entry (includes "(INSERTED)" marker)
- [ ] Phase inserted in correct position (after target phase, before next integer phase)
- [ ] STATE.md updated with roadmap evolution note
- [ ] Decimal number calculated correctly (based on existing decimals)
- [ ] User informed of next steps and dependency implications
<\/success_criteria>}