How this skill is triggered — by the user, by Claude, or both
Slash command
/mindforge:mindforge-add-backlogThe 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=$(node ".agent/bin/mindforge-tools.cjs" phase next-decimal 999 --raw)
If no 999.x phases exist, start at 999.1.
Create the phase directory:
SLUG=$(node ".agent/bin/mindforge-tools.cjs" generate-slug "$ARGUMENTS")
mkdir -p ".planning/phases/${NEXT}-${SLUG}"
touch ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
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 /mindforge-review-backlog when ready)
Commit:
node ".agent/bin/mindforge-tools.cjs" commit "docs: add backlog item ${NEXT} — ${ARGUMENTS}" --files .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 /mindforge-discuss-phase {NEXT} to explore it further.
Use /mindforge-review-backlog to promote items to active milestone.
npx claudepluginhub sairam0424/mindforge --plugin mindforgeGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates 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.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.