The gsd_run resolver preamble now probes
<repo-root>/.claude/get-shit-done/bin/${_GSD_SHIM_NAME} as the second
check — immediately after the existing get-shit-done/bin/ check and
before command -v / $HOME/.claude fallbacks. This covers the install
layout produced by npx @opengsd/get-shit-done-redux@latest --claude --local.
A _GSD_RUNTIME_ROOT variable is introduced to bind the repo-root
expression once and reuse it for both checks without repeating the
git rev-parse subshell.
76 workflow files regenerated via node scripts/sync-runtime-launcher.cjs.
All parity, size-budget, and new regression tests pass.
Co-authored-by: CI Rebase Check <ci@gsd-redux>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
157 lines
4.8 KiB
Markdown
157 lines
4.8 KiB
Markdown
<purpose>
|
|
Remove an unstarted future phase from the project roadmap, delete its directory, renumber all subsequent phases to maintain a clean linear sequence, and commit the change. The git commit serves as the historical record of removal.
|
|
</purpose>
|
|
|
|
<required_reading>
|
|
Read all files referenced by the invoking prompt's execution_context before starting.
|
|
</required_reading>
|
|
|
|
<process>
|
|
|
|
<step name="parse_arguments">
|
|
Parse the command arguments:
|
|
- Argument is the phase number to remove (integer or decimal)
|
|
- Example: `/gsd-remove-phase 17` → phase = 17
|
|
- Example: `/gsd-remove-phase 16.1` → phase = 16.1
|
|
|
|
If no argument provided:
|
|
|
|
```
|
|
ERROR: Phase number required
|
|
Usage: /gsd-remove-phase <phase-number>
|
|
Example: /gsd-remove-phase 17
|
|
```
|
|
|
|
Exit.
|
|
</step>
|
|
|
|
<step name="init_context">
|
|
Load phase operation context:
|
|
|
|
```bash
|
|
_GSD_SHIM_NAME="gsd-tools.cjs"; _GSD_RUNTIME_ROOT="${RUNTIME_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}"; GSD_TOOLS="${_GSD_RUNTIME_ROOT}/get-shit-done/bin/${_GSD_SHIM_NAME}"; if [ -f "$GSD_TOOLS" ]; then gsd_run() { node "$GSD_TOOLS" "$@"; }; elif [ -f "${_GSD_RUNTIME_ROOT}/.claude/get-shit-done/bin/${_GSD_SHIM_NAME}" ]; then GSD_TOOLS="${_GSD_RUNTIME_ROOT}/.claude/get-shit-done/bin/${_GSD_SHIM_NAME}"; gsd_run() { node "$GSD_TOOLS" "$@"; }; elif command -v gsd-tools >/dev/null 2>&1; then GSD_TOOLS="$(command -v gsd-tools)"; gsd_run() { "$GSD_TOOLS" "$@"; }; elif [ -f "$HOME/.claude/get-shit-done/bin/${_GSD_SHIM_NAME}" ]; then GSD_TOOLS="$HOME/.claude/get-shit-done/bin/${_GSD_SHIM_NAME}"; gsd_run() { node "$GSD_TOOLS" "$@"; }; else echo "ERROR: gsd-tools.cjs not found at $GSD_TOOLS and gsd-tools is not on PATH. Run: npx -y @opengsd/get-shit-done-redux@latest --claude --local" >&2; exit 1; fi
|
|
INIT=$(gsd_run query init.phase-op "${target}")
|
|
if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
|
|
```
|
|
|
|
Extract: `phase_found`, `phase_dir`, `phase_number`, `commit_docs`, `roadmap_exists`.
|
|
|
|
Also read STATE.md and ROADMAP.md content for parsing current position.
|
|
</step>
|
|
|
|
<step name="validate_future_phase">
|
|
Verify the phase is a future phase (not started):
|
|
|
|
1. Compare target phase to current phase from STATE.md
|
|
2. Target must be > current phase number
|
|
|
|
If target <= current phase:
|
|
|
|
```
|
|
ERROR: Cannot remove Phase {target}
|
|
|
|
Only future phases can be removed:
|
|
- Current phase: {current}
|
|
- Phase {target} is current or completed
|
|
|
|
To abandon current work, use /gsd:pause-work instead.
|
|
```
|
|
|
|
Exit.
|
|
</step>
|
|
|
|
<step name="confirm_removal">
|
|
Present removal summary and confirm:
|
|
|
|
```
|
|
Removing Phase {target}: {Name}
|
|
|
|
This will:
|
|
- Delete: .planning/phases/{target}-{slug}/
|
|
- Renumber all subsequent phases
|
|
- Update: ROADMAP.md, STATE.md
|
|
|
|
Proceed? (y/n)
|
|
```
|
|
|
|
Wait for confirmation.
|
|
</step>
|
|
|
|
<step name="execute_removal">
|
|
**Delegate the entire removal operation to `gsd-tools.cjs query phase.remove`:**
|
|
|
|
```bash
|
|
RESULT=$(gsd_run query phase.remove "${target}")
|
|
```
|
|
|
|
If the phase has executed plans (SUMMARY.md files), the CLI will error. Use `--force` only if the user confirms:
|
|
|
|
```bash
|
|
RESULT=$(gsd_run query phase.remove "${target}" --force)
|
|
```
|
|
|
|
The CLI handles:
|
|
- Deleting the phase directory
|
|
- Renumbering all subsequent directories (in reverse order to avoid conflicts)
|
|
- Renaming all files inside renumbered directories (PLAN.md, SUMMARY.md, etc.)
|
|
- Updating ROADMAP.md (removing section, renumbering all phase references, updating dependencies)
|
|
- Updating STATE.md (decrementing phase count)
|
|
|
|
Extract from result: `removed`, `directory_deleted`, `renamed_directories`, `renamed_files`, `roadmap_updated`, `state_updated`.
|
|
</step>
|
|
|
|
<step name="commit">
|
|
Stage and commit the removal:
|
|
|
|
```bash
|
|
gsd_run query commit "chore: remove phase {target} ({original-phase-name})" --files .planning/
|
|
```
|
|
|
|
The commit message preserves the historical record of what was removed.
|
|
</step>
|
|
|
|
<step name="completion">
|
|
Present completion summary:
|
|
|
|
```
|
|
Phase {target} ({original-name}) removed.
|
|
|
|
Changes:
|
|
- Deleted: .planning/phases/{target}-{slug}/
|
|
- Renumbered: {N} directories and {M} files
|
|
- Updated: ROADMAP.md, STATE.md
|
|
- Committed: chore: remove phase {target} ({original-name})
|
|
|
|
---
|
|
|
|
## What's Next
|
|
|
|
Would you like to:
|
|
- `/gsd:progress` — see updated roadmap status
|
|
- Continue with current phase
|
|
- Review roadmap
|
|
|
|
---
|
|
```
|
|
</step>
|
|
|
|
</process>
|
|
|
|
<anti_patterns>
|
|
|
|
- Don't remove completed phases (have SUMMARY.md files) without --force
|
|
- Don't remove current or past phases
|
|
- Don't manually renumber — use `gsd-tools.cjs query phase.remove` which handles all renumbering
|
|
- Don't add "removed phase" notes to STATE.md — git commit is the record
|
|
- Don't modify completed phase directories
|
|
</anti_patterns>
|
|
|
|
<success_criteria>
|
|
Phase removal is complete when:
|
|
|
|
- [ ] Target phase validated as future/unstarted
|
|
- [ ] `gsd-tools.cjs query phase.remove` executed successfully
|
|
- [ ] Changes committed with descriptive message
|
|
- [ ] User informed of changes
|
|
</success_criteria>
|