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

Remove Phase

Name: remove-phase
Author: PauloHYBEX

Remove a future phase from the roadmap, delete its directory, and renumber subsequent phases to maintain a clean linear sequence.

Usage: remove-phase [N]

Only future phases can be removed. Completed phases (with SUMMARY.md files) require explicit confirmation. The git commit is the historical record of what was removed.

Step 1: Parse and Validate

Extract the phase number from arguments. If missing:

Usage: remove-phase [N]
Example: remove-phase 7

[N] = phase number to remove (integer or decimal like 3.1)

Check roadmap exists:

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

Step 2: Verify the Phase is Future

Read .planning/STATE.md to find the current phase number.

Read .planning/ROADMAP.md to confirm phase [N] exists.

If target phase ≤ current phase:

Cannot remove Phase [N].

Only future (unstarted) phases can be removed.
Current phase: [current]
Phase [N] is current or already completed.

To undo completed work: use git revert on the phase commits.

Stop.

Step 3: Check for Executed Work

ls ".planning/phases/[NN]-[slug]/"*-SUMMARY.md 2>/dev/null

If SUMMARY.md files exist, the phase has partially executed content. Warn:

⚠️  Phase [N] has [M] executed plan(s) with SUMMARY.md files.
Removing it will delete this work from the roadmap (git history preserves the commits).

Are you sure?
- Yes, remove it anyway
- No, keep it

Wait for confirmation before proceeding.

Step 4: Confirm Removal

Show what will happen:

Removing Phase [N]: [Name]

This will:
- Delete: .planning/phases/[NN]-[slug]/
- Renumber: Phases [N+1] through [max] → [N] through [max-1]
- Update: ROADMAP.md and STATE.md

Proceed? (yes/no)

Wait for explicit confirmation.

Step 5: Execute Removal

Delete the phase directory:

rm -rf ".planning/phases/[NN]-[slug]/"

Renumber subsequent phases:

For each phase directory after [N] (in reverse order to avoid conflicts):

# Example: phase 08 → 07, 09 → 08, etc.
for dir in $(ls .planning/phases/ | grep -E "^[0-9]" | sort -rV); do
  # extract number, if > removed phase number, decrement and rename
done

Also rename files inside each renamed directory (PLAN.md, SUMMARY.md, etc. that start with the old phase number).

Update ROADMAP.md:

Remove the phase [N] section entirely
Update all subsequent phase numbers and any Depends on references

Update STATE.md:

Decrement total phase count
Add to Roadmap Evolution: - Phase [N] ([name]) removed

Step 6: Commit

git add -A
git commit -m "chore(roadmap): remove phase [N] ([original-name])"

The commit message preserves the historical record.

Step 7: Confirm

Phase [N] ([original-name]) removed.

Changes made:
- Deleted: .planning/phases/[NN]-[slug]/
- Renumbered: [M] phases
- Updated: ROADMAP.md, STATE.md

▶ Next: progress (to see updated roadmap)

# Remove Phase Remove a future phase from the roadmap, delete its directory, and renumber subsequent phases to maintain a clean linear sequence. **Usage:** `remove-phase [N]` **Only future phases can be removed.** Completed phases (with SUMMARY.md files) require explicit confirmation. The git commit is the historical record of what was removed. ## Step 1: Parse and Validate Extract the phase number from arguments. If missing: ``` Usage: remove-phase [N] Example: remove-phase 7 [N] = phase number to remove (integer or decimal like 3.1) ``` Check roadmap exists: ```bash node -e "const fs=require('fs'); console.log(fs.existsSync('.planning/ROADMAP.md') ? 'OK' : 'MISSING')" ``` ## Step 2: Verify the Phase is Future Read `.planning/STATE.md` to find the current phase number. Read `.planning/ROADMAP.md` to confirm phase `[N]` exists. If target phase ≤ current phase: ``` Cannot remove Phase [N]. Only future (unstarted) phases can be removed. Current phase: [current] Phase [N] is current or already completed. To undo completed work: use git revert on the phase commits. ``` Stop. ## Step 3: Check for Executed Work ```bash ls ".planning/phases/[NN]-[slug]/"*-SUMMARY.md 2>/dev/null ``` If SUMMARY.md files exist, the phase has partially executed content. Warn: ``` ⚠️ Phase [N] has [M] executed plan(s) with SUMMARY.md files. Removing it will delete this work from the roadmap (git history preserves the commits). Are you sure? - Yes, remove it anyway - No, keep it ``` Wait for confirmation before proceeding. ## Step 4: Confirm Removal Show what will happen: ``` Removing Phase [N]: [Name] This will: - Delete: .planning/phases/[NN]-[slug]/ - Renumber: Phases [N+1] through [max] → [N] through [max-1] - Update: ROADMAP.md and STATE.md Proceed? (yes/no) ``` Wait for explicit confirmation. ## Step 5: Execute Removal **Delete the phase directory:** ```bash rm -rf ".planning/phases/[NN]-[slug]/" ``` **Renumber subsequent phases:** For each phase directory after `[N]` (in reverse order to avoid conflicts): ```bash # Example: phase 08 → 07, 09 → 08, etc. for dir in $(ls .planning/phases/ | grep -E "^[0-9]" | sort -rV); do # extract number, if > removed phase number, decrement and rename done ``` Also rename files inside each renamed directory (PLAN.md, SUMMARY.md, etc. that start with the old phase number). **Update ROADMAP.md:** - Remove the phase `[N]` section entirely - Update all subsequent phase numbers and any `Depends on` references **Update STATE.md:** - Decrement total phase count - Add to Roadmap Evolution: `- Phase [N] ([name]) removed` ## Step 6: Commit ```bash git add -A git commit -m "chore(roadmap): remove phase [N] ([original-name])" ``` The commit message preserves the historical record. ## Step 7: Confirm ``` Phase [N] ([original-name]) removed. Changes made: - Deleted: .planning/phases/[NN]-[slug]/ - Renumbered: [M] phases - Updated: ROADMAP.md, STATE.md ▶ Next: progress (to see updated roadmap) ```

{ "prompt": "# Remove Phase\n\nRemove a future phase from the roadmap, delete its directory, and renumber subsequent phases to maintain a clean linear sequence.\n\n**Usage:** `remove-phase [N]`\n\n**Only future phases can be removed.** Completed phases (with SUMMARY.md files) require explicit confirmation. The git commit is the historical record of what was removed.\n\n## Step 1: Parse and Validate\n\nExtract the phase number from arguments. If missing:\n```\nUsage: remove-phase [N]\nExample: remove-phase 7\n\n[N] = phase number to remove (integer or decimal like 3.1)\n```\n\nCheck roadmap exists:\n```bash\nnode -e \"const fs=require('fs'); console.log(fs.existsSync('.planning/ROADMAP.md') ? 'OK' : 'MISSING')\"\n```\n\n## Step 2: Verify the Phase is Future\n\nRead `.planning/STATE.md` to find the current phase number.\n\nRead `.planning/ROADMAP.md` to confirm phase `[N]` exists.\n\nIf target phase ≤ current phase:\n```\nCannot remove Phase [N].\n\nOnly future (unstarted) phases can be removed.\nCurrent phase: [current]\nPhase [N] is current or already completed.\n\nTo undo completed work: use git revert on the phase commits.\n```\n\nStop.\n\n## Step 3: Check for Executed Work\n\n```bash\nls \".planning/phases/[NN]-[slug]/\"*-SUMMARY.md 2>/dev/null\n```\n\nIf SUMMARY.md files exist, the phase has partially executed content. Warn:\n```\n⚠️ Phase [N] has [M] executed plan(s) with SUMMARY.md files.\nRemoving it will delete this work from the roadmap (git history preserves the commits).\n\nAre you sure?\n- Yes, remove it anyway\n- No, keep it\n```\n\nWait for confirmation before proceeding.\n\n## Step 4: Confirm Removal\n\nShow what will happen:\n```\nRemoving Phase [N]: [Name]\n\nThis will:\n- Delete: .planning/phases/[NN]-[slug]/\n- Renumber: Phases [N+1] through [max] → [N] through [max-1]\n- Update: ROADMAP.md and STATE.md\n\nProceed? (yes/no)\n```\n\nWait for explicit confirmation.\n\n## Step 5: Execute Removal\n\n**Delete the phase directory:**\n```bash\nrm -rf \".planning/phases/[NN]-[slug]/\"\n```\n\n**Renumber subsequent phases:**\n\nFor each phase directory after `[N]` (in reverse order to avoid conflicts):\n```bash\n# Example: phase 08 → 07, 09 → 08, etc.\nfor dir in $(ls .planning/phases/ | grep -E \"^[0-9]\" | sort -rV); do\n # extract number, if > removed phase number, decrement and rename\ndone\n```\n\nAlso rename files inside each renamed directory (PLAN.md, SUMMARY.md, etc. that start with the old phase number).\n\n**Update ROADMAP.md:**\n- Remove the phase `[N]` section entirely\n- Update all subsequent phase numbers and any `Depends on` references\n\n**Update STATE.md:**\n- Decrement total phase count\n- Add to Roadmap Evolution: `- Phase [N] ([name]) removed`\n\n## Step 6: Commit\n\n```bash\ngit add -A\ngit commit -m \"chore(roadmap): remove phase [N] ([original-name])\"\n```\n\nThe commit message preserves the historical record.\n\n## Step 7: Confirm\n\n```\nPhase [N] ([original-name]) removed.\n\nChanges made:\n- Deleted: .planning/phases/[NN]-[slug]/\n- Renumbered: [M] phases\n- Updated: ROADMAP.md, STATE.md\n\n▶ Next: progress (to see updated roadmap)\n```", "variables": [], "notes": "Remove a planned (not yet executed) phase and renumber subsequent phases", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/PauloHYBEX/Nexus-TCMS", "path": ".windsurf/workflows/remove-phase.md", "ref": "af66d4e66d7443d045e74bafc302cd998ceb5b99", "url": "https://github.com/PauloHYBEX/Nexus-TCMS/blob/af66d4e66d7443d045e74bafc302cd998ceb5b99/.windsurf/workflows/remove-phase.md", "key": "PauloHYBEX/Nexus-TCMS/.windsurf/workflows/remove-phase.md" } } }

remove-phase

About

Remove Phase

Step 1: Parse and Validate

Step 2: Verify the Phase is Future

Step 3: Check for Executed Work

Step 4: Confirm Removal

Step 5: Execute Removal

Step 6: Commit

Step 7: Confirm

Use it

Manifest

Reviews