73c1af5168
Commands are now installed as commands/gsd/<name>.md and invoked as /gsd:<name> in Claude Code. The old hyphen form /gsd-<name> was still hardcoded in hundreds of places across workflows, references, templates, lib modules, and command files — causing "Unknown command" errors whenever GSD suggested a command to the user. Replace all /gsd-<cmd> occurrences where <cmd> is a known command name (derived at runtime from commands/gsd/*.md) using a targeted Node.js script. Agent names, tool names (gsd-sdk, gsd-tools), directory names, and path fragments are not touched. Adds regression test tests/bug-2543-gsd-slash-namespace.test.cjs that enforces zero legacy occurrences going forward. Removes inverted tests/stale-colon-refs.test.cjs (bug #1748) which enforced the now-obsolete hyphen form; the new bug-2543 test supersedes it. Updates 5 assertion tests that hardcoded the old hyphen form to accept the new colon form. Closes #2543 Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
113 lines
2.7 KiB
Markdown
113 lines
2.7 KiB
Markdown
<purpose>
|
|
Add a new integer phase to the end of the current milestone in the roadmap. Automatically calculates next phase number, creates phase directory, and updates roadmap structure.
|
|
</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:
|
|
- All arguments become the phase description
|
|
- Example: `/gsd:add-phase Add authentication` → description = "Add authentication"
|
|
- Example: `/gsd:add-phase Fix critical performance issues` → description = "Fix critical performance issues"
|
|
|
|
If no arguments provided:
|
|
|
|
```
|
|
ERROR: Phase description required
|
|
Usage: /gsd:add-phase <description>
|
|
Example: /gsd:add-phase Add authentication system
|
|
```
|
|
|
|
Exit.
|
|
</step>
|
|
|
|
<step name="init_context">
|
|
Load phase operation context:
|
|
|
|
```bash
|
|
INIT=$(gsd-sdk query init.phase-op "0")
|
|
if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
|
|
```
|
|
|
|
Check `roadmap_exists` from init JSON. If false:
|
|
```
|
|
ERROR: No roadmap found (.planning/ROADMAP.md)
|
|
Run /gsd:new-project to initialize.
|
|
```
|
|
Exit.
|
|
</step>
|
|
|
|
<step name="add_phase">
|
|
**Delegate the phase addition to `gsd-sdk query phase.add`:**
|
|
|
|
```bash
|
|
RESULT=$(gsd-sdk query phase.add "${description}")
|
|
```
|
|
|
|
The CLI handles:
|
|
- Finding the highest existing integer phase number
|
|
- Calculating next phase number (max + 1)
|
|
- Generating slug from description
|
|
- Creating the phase directory (`.planning/phases/{NN}-{slug}/`)
|
|
- Inserting the phase entry into ROADMAP.md with Goal, Depends on, and Plans sections
|
|
|
|
Extract from result: `phase_number`, `padded`, `name`, `slug`, `directory`.
|
|
</step>
|
|
|
|
<step name="update_project_state">
|
|
Update STATE.md to reflect the new phase:
|
|
|
|
1. Read `.planning/STATE.md`
|
|
2. Under "## Accumulated Context" → "### Roadmap Evolution" add entry:
|
|
```
|
|
- Phase {N} added: {description}
|
|
```
|
|
|
|
If "Roadmap Evolution" section doesn't exist, create it.
|
|
</step>
|
|
|
|
<step name="completion">
|
|
Present completion summary:
|
|
|
|
```
|
|
Phase {N} added to current milestone:
|
|
- Description: {description}
|
|
- Directory: .planning/phases/{phase-num}-{slug}/
|
|
- Status: Not planned yet
|
|
|
|
Roadmap updated: .planning/ROADMAP.md
|
|
|
|
---
|
|
|
|
## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
|
|
|
|
**Phase {N}: {description}**
|
|
|
|
`/clear` then:
|
|
|
|
`/gsd:plan-phase {N}`
|
|
|
|
---
|
|
|
|
**Also available:**
|
|
- `/gsd:add-phase <description>` — add another phase
|
|
- Review roadmap
|
|
|
|
---
|
|
```
|
|
</step>
|
|
|
|
</process>
|
|
|
|
<success_criteria>
|
|
- [ ] `gsd-sdk query phase.add` executed successfully
|
|
- [ ] Phase directory created
|
|
- [ ] Roadmap updated with new phase entry
|
|
- [ ] STATE.md updated with roadmap evolution note
|
|
- [ ] User informed of next steps
|
|
</success_criteria>
|