How this skill is triggered — by the user, by Claude, or both
Slash command
/bm:add-backlog <description><description>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<objective>
Read ROADMAP.md to find existing backlog entries:
cat .planning/ROADMAP.md
Find next backlog number:
NEXT=$(gsd-sdk query phase.next-decimal 999 --raw)
If no 999.x phases exist, start at 999.1.
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, so directory existence reliably means the phase is already registered (prevents false duplicate detection in hooks checking 999.x directories, #2280):
## Backlog
### Phase {NEXT}: {description} (BACKLOG)
**Goal:** [Captured for future planning]
**Requirements:** TBD
**Plans:** 0 plans
Plans:
- [ ] TBD (promote with /bm:review-backlog when ready)
Create the phase directory:
SLUG=$(gsd-sdk query generate-slug "$ARGUMENTS" --raw)
mkdir -p ".planning/phases/${NEXT}-${SLUG}"
touch ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
Commit:
gsd-sdk query commit "docs: add backlog item ${NEXT} — ${ARGUMENTS}" .planning/ROADMAP.md ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
Report:
## 📋 Backlog Item Added
Phase {NEXT}: {description}
Directory: .planning/phases/{NEXT}-{slug}/
This item lives in the backlog parking lot.
Use /bm:discuss-phase {NEXT} to explore it further.
Use /bm:review-backlog to promote items to active milestone.
npx claudepluginhub buildomator/buildomator --plugin bmCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.