ItsSalvatore/gsd-add-backlog

<cursor_skill_adapter>

A. Skill Invocation

• This skill is invoked when the user mentions gsd-add-backlog or describes a task matching this skill.
• Treat all user text after the skill mention as {{GSD_ARGS}}.
• If no arguments are present, treat {{GSD_ARGS}} as empty.

B. User Prompting

When the workflow needs user input, prompt the user conversationally:

• Present options as a numbered list in your response text
• Ask the user to reply with their choice
• For multi-select, ask for comma-separated numbers

C. Tool Usage

Use these Cursor tools when executing GSD workflows:

• Shell for running commands (terminal operations)
• StrReplace for editing existing files
• Read, Write, Glob, Grep, Task, WebSearch, WebFetch, TodoWrite as needed

D. Subagent Spawning

When the workflow needs to spawn a subagent:

• Use Task(subagent_type="generalPurpose", ...)
• The model parameter maps to Cursor's model options (e.g., "fast") </cursor_skill_adapter>

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

   cat .planning/ROADMAP.md
   

2. Find next backlog number:

   NEXT=$(node "C:/Users/mano/Desktop/PKHEX!/.cursor/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:

   SLUG=$(node "C:/Users/mano/Desktop/PKHEX!/.cursor/get-shit-done/bin/gsd-tools.cjs" generate-slug "{{GSD_ARGS}}")
   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:

   node "C:/Users/mano/Desktop/PKHEX!/.cursor/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>