Prompt file imported from PauloHYBEX/Nexus-TCMS (.windsurf/workflows/add-phase.md). Fill in {{NEXT_NUM}}, {{SLUG}} before use. Copyright stays with the author.

Add Phase

Name: add-phase
Author: PauloHYBEX

Append a new integer phase to the end of the current milestone. Use when scope grows after initial planning — a new feature, an unplanned integration, or a discovered dependency.

Usage: add-phase [description]

Step 1: Validate

Check that a roadmap exists:

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

If missing: stop — run new-project first.

If no description was provided as an argument, ask: "What does this new phase deliver?"

Step 2: Find Next Phase Number

Read .planning/ROADMAP.md and find the highest existing integer phase number:

grep -E "^## Phase [0-9]+" .planning/ROADMAP.md | tail -1
# PowerShell: Select-String -Path .planning/ROADMAP.md -Pattern '^## Phase \d+' | Select-Object -Last 1

Also scan the phases directory for any directories that may not be in the roadmap:

ls .planning/phases/ 2>/dev/null | grep -E "^[0-9]+" | sort -n | tail -3
# PowerShell: Get-ChildItem .planning/phases/ -ErrorAction SilentlyContinue | Where-Object { $_.Name -match '^[0-9]+' } | Sort-Object Name | Select-Object -Last 3

Set NEXT_NUM = highest found + 1. Pad to 2 digits (01, 02, ..., 10, 11, ...).

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

Step 3: Create Phase Directory

node -e "require('fs').mkdirSync('.planning/phases/{{NEXT_NUM}}-{{SLUG}}',{recursive:true})"
# PowerShell: New-Item -ItemType Directory -Force -Path ".planning/phases/{{NEXT_NUM}}-{{SLUG}}"

Step 4: Update ROADMAP.md

Append the new phase entry to ROADMAP.md:

## Phase [N]: [Description]

**Goal:** [One sentence — what user can do after this phase]
**Status:** [ ] Not started
**Depends on:** Phase [N-1]

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

Step 5: Update STATE.md

Add to the "Roadmap Evolution" section under Accumulated Context (create if missing):

### Roadmap Evolution
- Phase [N] added: [description]

Step 6: Commit

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

Step 7: Confirm

Phase [N] added: [description]

Directory: .planning/phases/[NN]-[slug]/
Status: Not planned yet
Roadmap: .planning/ROADMAP.md updated

▶ Next: plan-phase [N]

# Add Phase Append a new integer phase to the end of the current milestone. Use when scope grows after initial planning — a new feature, an unplanned integration, or a discovered dependency. **Usage:** `add-phase [description]` ## Step 1: Validate Check that a roadmap exists: ```bash node -e "const fs=require('fs'); console.log(fs.existsSync('.planning/ROADMAP.md') ? 'OK' : 'MISSING')" ``` If missing: stop — run `new-project` first. If no description was provided as an argument, ask: "What does this new phase deliver?" ## Step 2: Find Next Phase Number Read `.planning/ROADMAP.md` and find the highest existing integer phase number: ```bash grep -E "^## Phase [0-9]+" .planning/ROADMAP.md | tail -1 # PowerShell: Select-String -Path .planning/ROADMAP.md -Pattern '^## Phase \d+' | Select-Object -Last 1 ``` Also scan the phases directory for any directories that may not be in the roadmap: ```bash ls .planning/phases/ 2>/dev/null | grep -E "^[0-9]+" | sort -n | tail -3 # PowerShell: Get-ChildItem .planning/phases/ -ErrorAction SilentlyContinue | Where-Object { $_.Name -match '^[0-9]+' } | Sort-Object Name | Select-Object -Last 3 ``` Set `NEXT_NUM` = highest found + 1. Pad to 2 digits (01, 02, ..., 10, 11, ...). Generate a slug from the description (lowercase, hyphens, max 40 chars). ## Step 3: Create Phase Directory ```bash node -e "require('fs').mkdirSync('.planning/phases/{{NEXT_NUM}}-{{SLUG}}',{recursive:true})" # PowerShell: New-Item -ItemType Directory -Force -Path ".planning/phases/{{NEXT_NUM}}-{{SLUG}}" ``` ## Step 4: Update ROADMAP.md Append the new phase entry to ROADMAP.md: ```markdown ## Phase [N]: [Description] **Goal:** [One sentence — what user can do after this phase] **Status:** [ ] Not started **Depends on:** Phase [N-1] ### Plans *Not yet planned — run `plan-phase [N]`* ``` ## Step 5: Update STATE.md Add to the "Roadmap Evolution" section under Accumulated Context (create if missing): ```markdown ### Roadmap Evolution - Phase [N] added: [description] ``` ## Step 6: Commit ```bash git add .planning/ROADMAP.md .planning/STATE.md git commit -m "chore(roadmap): add phase [N] — [description]" ``` ## Step 7: Confirm ``` Phase [N] added: [description] Directory: .planning/phases/[NN]-[slug]/ Status: Not planned yet Roadmap: .planning/ROADMAP.md updated ▶ Next: plan-phase [N] ```

{ "prompt": "# Add Phase\n\nAppend a new integer phase to the end of the current milestone. Use when scope grows after initial planning — a new feature, an unplanned integration, or a discovered dependency.\n\n**Usage:** `add-phase [description]`\n\n## Step 1: Validate\n\nCheck that a roadmap exists:\n```bash\nnode -e \"const fs=require('fs'); console.log(fs.existsSync('.planning/ROADMAP.md') ? 'OK' : 'MISSING')\"\n```\n\nIf missing: stop — run `new-project` first.\n\nIf no description was provided as an argument, ask: \"What does this new phase deliver?\"\n\n## Step 2: Find Next Phase Number\n\nRead `.planning/ROADMAP.md` and find the highest existing integer phase number:\n```bash\ngrep -E \"^## Phase [0-9]+\" .planning/ROADMAP.md | tail -1\n# PowerShell: Select-String -Path .planning/ROADMAP.md -Pattern '^## Phase \\d+' | Select-Object -Last 1\n```\n\nAlso scan the phases directory for any directories that may not be in the roadmap:\n```bash\nls .planning/phases/ 2>/dev/null | grep -E \"^[0-9]+\" | sort -n | tail -3\n# PowerShell: Get-ChildItem .planning/phases/ -ErrorAction SilentlyContinue | Where-Object { $_.Name -match '^[0-9]+' } | Sort-Object Name | Select-Object -Last 3\n```\n\nSet `NEXT_NUM` = highest found + 1. Pad to 2 digits (01, 02, ..., 10, 11, ...).\n\nGenerate a slug from the description (lowercase, hyphens, max 40 chars).\n\n## Step 3: Create Phase Directory\n\n```bash\nnode -e \"require('fs').mkdirSync('.planning/phases/{{NEXT_NUM}}-{{SLUG}}',{recursive:true})\"\n# PowerShell: New-Item -ItemType Directory -Force -Path \".planning/phases/{{NEXT_NUM}}-{{SLUG}}\"\n```\n\n## Step 4: Update ROADMAP.md\n\nAppend the new phase entry to ROADMAP.md:\n\n```markdown\n## Phase [N]: [Description]\n\n**Goal:** [One sentence — what user can do after this phase]\n**Status:** [ ] Not started\n**Depends on:** Phase [N-1]\n\n### Plans\n*Not yet planned — run `plan-phase [N]`*\n```\n\n## Step 5: Update STATE.md\n\nAdd to the \"Roadmap Evolution\" section under Accumulated Context (create if missing):\n```markdown\n### Roadmap Evolution\n- Phase [N] added: [description]\n```\n\n## Step 6: Commit\n\n```bash\ngit add .planning/ROADMAP.md .planning/STATE.md\ngit commit -m \"chore(roadmap): add phase [N] — [description]\"\n```\n\n## Step 7: Confirm\n\n```\nPhase [N] added: [description]\n\nDirectory: .planning/phases/[NN]-[slug]/\nStatus: Not planned yet\nRoadmap: .planning/ROADMAP.md updated\n\n▶ Next: plan-phase [N]\n```", "variables": [ "NEXT_NUM", "SLUG" ], "notes": "Append a new phase to the current milestone roadmap when scope grows after initial planning", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/PauloHYBEX/Nexus-TCMS", "path": ".windsurf/workflows/add-phase.md", "ref": "af66d4e66d7443d045e74bafc302cd998ceb5b99", "url": "https://github.com/PauloHYBEX/Nexus-TCMS/blob/af66d4e66d7443d045e74bafc302cd998ceb5b99/.windsurf/workflows/add-phase.md", "key": "PauloHYBEX/Nexus-TCMS/.windsurf/workflows/add-phase.md" } } }

add-phase

About

Add Phase

Step 1: Validate

Step 2: Find Next Phase Number

Step 3: Create Phase Directory

Step 4: Update ROADMAP.md

Step 5: Update STATE.md

Step 6: Commit

Step 7: Confirm

Use it

Manifest

Reviews