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>
80 lines
2.3 KiB
Markdown
80 lines
2.3 KiB
Markdown
---
|
|
name: gsd:add-backlog
|
|
description: Add an idea to the backlog parking lot (999.x numbering)
|
|
argument-hint: <description>
|
|
allowed-tools:
|
|
- Read
|
|
- Write
|
|
- Bash
|
|
---
|
|
|
|
<objective>
|
|
Add a backlog item to the roadmap using 999.x numbering. Backlog items are
|
|
unsequenced ideas that aren't ready for active planning — they live outside
|
|
the normal phase sequence and accumulate context over time.
|
|
</objective>
|
|
|
|
<process>
|
|
|
|
1. **Read ROADMAP.md** to find existing backlog entries:
|
|
```bash
|
|
cat .planning/ROADMAP.md
|
|
```
|
|
|
|
2. **Find next backlog number:**
|
|
```bash
|
|
NEXT=$(gsd-sdk query phase.next-decimal 999 --raw)
|
|
```
|
|
If no 999.x phases exist, start at 999.1.
|
|
|
|
3. **Add to ROADMAP.md** under a `## Backlog` section. If the section doesn't exist, create it at the end.
|
|
Write the ROADMAP entry BEFORE creating the directory — this ensures directory existence is always
|
|
a reliable indicator that the phase is already registered, which prevents false duplicate detection
|
|
in any hook that checks for existing 999.x directories (#2280):
|
|
|
|
```markdown
|
|
## Backlog
|
|
|
|
### Phase {NEXT}: {description} (BACKLOG)
|
|
|
|
**Goal:** [Captured for future planning]
|
|
**Requirements:** TBD
|
|
**Plans:** 0 plans
|
|
|
|
Plans:
|
|
- [ ] TBD (promote with /gsd:review-backlog when ready)
|
|
```
|
|
|
|
4. **Create the phase directory:**
|
|
```bash
|
|
SLUG=$(gsd-sdk query generate-slug "$ARGUMENTS" --raw)
|
|
mkdir -p ".planning/phases/${NEXT}-${SLUG}"
|
|
touch ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
|
|
```
|
|
|
|
5. **Commit:**
|
|
```bash
|
|
gsd-sdk query commit "docs: add backlog item ${NEXT} — ${ARGUMENTS}" .planning/ROADMAP.md ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
|
|
```
|
|
|
|
6. **Report:**
|
|
```
|
|
## 📋 Backlog Item Added
|
|
|
|
Phase {NEXT}: {description}
|
|
Directory: .planning/phases/{NEXT}-{slug}/
|
|
|
|
This item lives in the backlog parking lot.
|
|
Use /gsd:discuss-phase {NEXT} to explore it further.
|
|
Use /gsd:review-backlog to promote items to active milestone.
|
|
```
|
|
|
|
</process>
|
|
|
|
<notes>
|
|
- 999.x numbering keeps backlog items out of the active phase sequence
|
|
- Phase directories are created immediately, so /gsd:discuss-phase and /gsd:plan-phase work on them
|
|
- No `Depends on:` field — backlog items are unsequenced by definition
|
|
- Sparse numbering is fine (999.1, 999.3) — always uses next-decimal
|
|
</notes>
|