d4767ac2e0
* fix: replace /gsd: command format with /gsd- skill format in all suggestions All next-step suggestions shown to users were still using the old colon format (/gsd:xxx) which cannot be copy-pasted as skills. Migrated all occurrences across agents/, commands/, get-shit-done/, docs/, README files, bin/install.js (hardcoded defaults for claude runtime), and get-shit-done/bin/lib/*.cjs (generate-claude-md templates and error messages). Updated tests to assert new hyphen format instead of old colon format. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: migrate remaining /gsd: format to /gsd- in hooks, workflows, and sdk Addresses remaining user-facing occurrences missed in the initial migration: - hooks/: fix 4 user-facing messages (pause-work, update, fast, quick) and 2 comments in gsd-workflow-guard.js - get-shit-done/workflows/: fix 21 Skill() literal calls that Claude executes directly (installer does not transform workflow content) - sdk/prompt-sanitizer.ts: update regex to strip /gsd- format in addition to legacy /gsd: format; update JSDoc comment - tests/: update autonomous-ui-steps, prompt-sanitizer to assert new format Note: commands/gsd/*.md frontmatter (name: gsd:xxx) intentionally unchanged — installer derives skillName from directory path, not the name field. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(plan-phase): preserve --chain flag in auto-advance sync and handle ui-phase gate in chain mode Bug 1: step 15 sync-flag check only guarded against --auto, causing _auto_chain_active to be cleared when plan-phase is invoked without --auto in ARGUMENTS even though a --chain pipeline was active. Added --chain to the guard condition, matching discuss-phase behaviour. Bug 2: UI Design Contract gate (step 5.6) always exited the workflow when UI-SPEC was missing, breaking the discuss --chain pipeline silently. When _auto_chain_active is true, the gate now auto-invokes gsd-ui-phase --auto via Skill() and continues to step 6 without prompting. Manual invocations retain the existing AskUserQuestion flow. * fix: remove <sub>/clear</sub> pattern and duplicate old-format command in discuss-phase.md --------- Co-authored-by: Claude Opus 4.6 <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=$(node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" 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-tools:**
|
|
|
|
```bash
|
|
RESULT=$(node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" 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
|
|
|
|
**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-tools 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>
|