Prompt file imported from PauloHYBEX/Nexus-TCMS (.windsurf/workflows/insert-phase.md). Copyright stays with the author.

Insert Phase

Name: insert-phase
Author: PauloHYBEX

Insert a decimal phase for urgent work discovered mid-milestone. Uses decimal numbering (e.g., 3.1) to preserve the logical sequence of planned phases without renumbering everything.

Usage: insert-phase [N] [description]

When to use: Urgent bug fix, critical dependency discovered, security patch — work that must happen between two existing phases without waiting.

Not for: Regular scope additions → use add-phase for those.

Step 1: Parse Arguments

Extract from arguments:

First token: the integer phase number to insert after (e.g., 3)
Remaining text: phase description

If either is missing:

Usage: insert-phase [N] [description]
Example: insert-phase 3 Fix critical auth vulnerability

[N] = phase to insert after (must be an existing phase)

Validate that the after-phase number is an integer.

Step 2: Validate

node -e "const fs=require('fs'); console.log(fs.existsSync('.planning/ROADMAP.md') ? 'OK' : 'MISSING')"

Check that phase [N] exists in ROADMAP.md:

grep -E "^## Phase [N]:" .planning/ROADMAP.md

If phase not found, list available phases and stop.

Step 3: Calculate Decimal Number

Find existing decimal phases after phase [N]:

ls .planning/phases/ 2>/dev/null | grep -E "^[N]\." | sort -V

If none exist → new phase is [N].1 If [N].1 exists → new phase is [N].2, etc.

Generate slug from description (lowercase, hyphens, max 40 chars).

Step 4: Create Phase Directory

node -e "require('fs').mkdirSync('.planning/phases/[N].[M]-[SLUG]',{recursive:true})"

Step 5: Update ROADMAP.md

Insert the decimal phase entry immediately after Phase [N] in ROADMAP.md:

## Phase [N].[M]: [Description] *(INSERTED — urgent)*

**Goal:** [One sentence — what this urgent work delivers]
**Status:** [ ] Not started
**Depends on:** Phase [N]
**Note:** Inserted between Phase [N] and Phase [N+1]

### Plans
*Not yet planned — run `plan-phase [N].[M]`*

Step 6: Update STATE.md

Add to Roadmap Evolution section:

- Phase [N].[M] inserted after Phase [N]: [description] (URGENT)

Note: Check if Phase [N+1] dependencies are still valid — the inserted phase may need to complete before [N+1] can run.

Step 7: Commit

git add .planning/ROADMAP.md .planning/STATE.md ".planning/phases/[N].[M]-[SLUG]/"
git commit -m "chore(roadmap): insert urgent phase [N].[M] — [description]"

Step 8: Confirm

Phase [N].[M] inserted after Phase [N]:

Description: [description]
Directory: .planning/phases/[N].[M]-[slug]/
Status: Not planned yet (URGENT)

⚠️  Check Phase [N+1] dependencies — does it still make sense to run after [N].[M]?

▶ Next: plan-phase [N].[M]

# Insert Phase Insert a decimal phase for urgent work discovered mid-milestone. Uses decimal numbering (e.g., `3.1`) to preserve the logical sequence of planned phases without renumbering everything. **Usage:** `insert-phase [N] [description]` **When to use:** Urgent bug fix, critical dependency discovered, security patch — work that must happen between two existing phases without waiting. **Not for:** Regular scope additions → use `add-phase` for those. ## Step 1: Parse Arguments Extract from arguments: - First token: the integer phase number to insert **after** (e.g., `3`) - Remaining text: phase description If either is missing: ``` Usage: insert-phase [N] [description] Example: insert-phase 3 Fix critical auth vulnerability [N] = phase to insert after (must be an existing phase) ``` Validate that the after-phase number is an integer. ## Step 2: Validate ```bash node -e "const fs=require('fs'); console.log(fs.existsSync('.planning/ROADMAP.md') ? 'OK' : 'MISSING')" ``` Check that phase `[N]` exists in ROADMAP.md: ```bash grep -E "^## Phase [N]:" .planning/ROADMAP.md ``` If phase not found, list available phases and stop. ## Step 3: Calculate Decimal Number Find existing decimal phases after phase `[N]`: ```bash ls .planning/phases/ 2>/dev/null | grep -E "^[N]\." | sort -V ``` If none exist → new phase is `[N].1` If `[N].1` exists → new phase is `[N].2`, etc. Generate slug from description (lowercase, hyphens, max 40 chars). ## Step 4: Create Phase Directory ```bash node -e "require('fs').mkdirSync('.planning/phases/[N].[M]-[SLUG]',{recursive:true})" ``` ## Step 5: Update ROADMAP.md Insert the decimal phase entry immediately after Phase `[N]` in ROADMAP.md: ```markdown ## Phase [N].[M]: [Description] *(INSERTED — urgent)* **Goal:** [One sentence — what this urgent work delivers] **Status:** [ ] Not started **Depends on:** Phase [N] **Note:** Inserted between Phase [N] and Phase [N+1] ### Plans *Not yet planned — run `plan-phase [N].[M]`* ``` ## Step 6: Update STATE.md Add to Roadmap Evolution section: ```markdown - Phase [N].[M] inserted after Phase [N]: [description] (URGENT) ``` Note: Check if Phase [N+1] dependencies are still valid — the inserted phase may need to complete before [N+1] can run. ## Step 7: Commit ```bash git add .planning/ROADMAP.md .planning/STATE.md ".planning/phases/[N].[M]-[SLUG]/" git commit -m "chore(roadmap): insert urgent phase [N].[M] — [description]" ``` ## Step 8: Confirm ``` Phase [N].[M] inserted after Phase [N]: Description: [description] Directory: .planning/phases/[N].[M]-[slug]/ Status: Not planned yet (URGENT) ⚠️ Check Phase [N+1] dependencies — does it still make sense to run after [N].[M]? ▶ Next: plan-phase [N].[M] ```

{ "prompt": "# Insert Phase\n\nInsert a decimal phase for urgent work discovered mid-milestone. Uses decimal numbering (e.g., `3.1`) to preserve the logical sequence of planned phases without renumbering everything.\n\n**Usage:** `insert-phase [N] [description]`\n\n**When to use:** Urgent bug fix, critical dependency discovered, security patch — work that must happen between two existing phases without waiting.\n\n**Not for:** Regular scope additions → use `add-phase` for those.\n\n## Step 1: Parse Arguments\n\nExtract from arguments:\n- First token: the integer phase number to insert **after** (e.g., `3`)\n- Remaining text: phase description\n\nIf either is missing:\n```\nUsage: insert-phase [N] [description]\nExample: insert-phase 3 Fix critical auth vulnerability\n\n[N] = phase to insert after (must be an existing phase)\n```\n\nValidate that the after-phase number is an integer.\n\n## Step 2: Validate\n\n```bash\nnode -e \"const fs=require('fs'); console.log(fs.existsSync('.planning/ROADMAP.md') ? 'OK' : 'MISSING')\"\n```\n\nCheck that phase `[N]` exists in ROADMAP.md:\n```bash\ngrep -E \"^## Phase [N]:\" .planning/ROADMAP.md\n```\n\nIf phase not found, list available phases and stop.\n\n## Step 3: Calculate Decimal Number\n\nFind existing decimal phases after phase `[N]`:\n```bash\nls .planning/phases/ 2>/dev/null | grep -E \"^[N]\\.\" | sort -V\n```\n\nIf none exist → new phase is `[N].1`\nIf `[N].1` exists → new phase is `[N].2`, etc.\n\nGenerate slug from description (lowercase, hyphens, max 40 chars).\n\n## Step 4: Create Phase Directory\n\n```bash\nnode -e \"require('fs').mkdirSync('.planning/phases/[N].[M]-[SLUG]',{recursive:true})\"\n```\n\n## Step 5: Update ROADMAP.md\n\nInsert the decimal phase entry immediately after Phase `[N]` in ROADMAP.md:\n\n```markdown\n## Phase [N].[M]: [Description] *(INSERTED — urgent)*\n\n**Goal:** [One sentence — what this urgent work delivers]\n**Status:** [ ] Not started\n**Depends on:** Phase [N]\n**Note:** Inserted between Phase [N] and Phase [N+1]\n\n### Plans\n*Not yet planned — run `plan-phase [N].[M]`*\n```\n\n## Step 6: Update STATE.md\n\nAdd to Roadmap Evolution section:\n```markdown\n- Phase [N].[M] inserted after Phase [N]: [description] (URGENT)\n```\n\nNote: Check if Phase [N+1] dependencies are still valid — the inserted phase may need to complete before [N+1] can run.\n\n## Step 7: Commit\n\n```bash\ngit add .planning/ROADMAP.md .planning/STATE.md \".planning/phases/[N].[M]-[SLUG]/\"\ngit commit -m \"chore(roadmap): insert urgent phase [N].[M] — [description]\"\n```\n\n## Step 8: Confirm\n\n```\nPhase [N].[M] inserted after Phase [N]:\n\nDescription: [description]\nDirectory: .planning/phases/[N].[M]-[slug]/\nStatus: Not planned yet (URGENT)\n\n⚠️ Check Phase [N+1] dependencies — does it still make sense to run after [N].[M]?\n\n▶ Next: plan-phase [N].[M]\n```", "variables": [], "notes": "Insert a new phase between existing phases for urgent work discovered mid-milestone", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/PauloHYBEX/Nexus-TCMS", "path": ".windsurf/workflows/insert-phase.md", "ref": "af66d4e66d7443d045e74bafc302cd998ceb5b99", "url": "https://github.com/PauloHYBEX/Nexus-TCMS/blob/af66d4e66d7443d045e74bafc302cd998ceb5b99/.windsurf/workflows/insert-phase.md", "key": "PauloHYBEX/Nexus-TCMS/.windsurf/workflows/insert-phase.md" } } }

insert-phase

About

Insert Phase

Step 1: Parse Arguments

Step 2: Validate

Step 3: Calculate Decimal Number

Step 4: Create Phase Directory

Step 5: Update ROADMAP.md

Step 6: Update STATE.md

Step 7: Commit

Step 8: Confirm

Use it

Manifest

Reviews