LLMSkillHub
mirroredCopied from coco-research/coco under MIT. coco-research has not claimed this page, and is not affiliated with LLM SkillHub.

coco-research / gsd-add-backlog

Use when the user wants to park an idea or feature request that is not ready for active planning, or says add it to the backlog. Writes a 999.x entry to ROADMAP.md and creates its phase directory for later promotion.

0
SKILL.md
2.3 KB

<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" --raw)
    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:

     ## 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>