Three new commands for managing ideas and cross-session context: /gsd:add-backlog <description> Adds a 999.x numbered backlog item to ROADMAP.md. Creates phase directory immediately so /gsd:discuss-phase and /gsd:plan-phase work on them. No dependencies, no sequencing — pure parking lot. /gsd:review-backlog Lists all 999.x items, lets user promote to active milestone, keep, or remove. Promotion renumbers to next sequential phase with proper deps. /gsd:thread [name | description] Three modes: - No args: list all threads with status - Existing name: resume thread, load context - New description: create thread from current conversation context Threads live in .planning/threads/ as lightweight markdown files with Goal, Context, References, and Next Steps sections. Design: - Self-contained command files, no core changes needed - 999.x numbering keeps backlog out of active sequence - Threads are independent of phases — cross-session knowledge stores - Both features compose with existing GSD commands Fixes #1005
77 lines
2.1 KiB
Markdown
77 lines
2.1 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=$(node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" phase next-decimal 999 --raw)
|
|
```
|
|
If no 999.x phases exist, start at 999.1.
|
|
|
|
3. **Create the phase directory:**
|
|
```bash
|
|
SLUG=$(node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" generate-slug "$ARGUMENTS")
|
|
mkdir -p ".planning/phases/${NEXT}-${SLUG}"
|
|
touch ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
|
|
```
|
|
|
|
4. **Add to ROADMAP.md** under a `## Backlog` section. If the section doesn't exist, create it at the end:
|
|
|
|
```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)
|
|
```
|
|
|
|
5. **Commit:**
|
|
```bash
|
|
node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" commit "docs: add backlog item ${NEXT} — ${ARGUMENTS}" --files .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>
|