Menu
Adds an idea to the backlog parking lot using 999.x numbering, kept outside the active phase sequence so it accumulates context without being scheduled. Use when an idea is worth keeping but not ready to plan into the current milestone.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.
Generate unit and E2E tests for a completed phase, using its SUMMARY, CONTEXT, and VERIFICATION artifacts as the spec and gating unit tests on a mutation check. Use when a finished phase needs test coverage; requires the phase number and an existing SUMMARY.md.
Analyze the current milestone's phase dependency graph (file overlap, semantic and data-flow links) and suggest Depends on entries for ROADMAP.md. Use before parallel phase execution to prevent merge conflicts from unordered phases.
Audit a milestone against its definition of done before archiving: aggregate per-phase VERIFICATION results, cross-check requirements coverage from three sources, spawn an integration checker for cross-phase wiring, and emit a structured audit report. Use when wrapping up a milestone, before /donny-complete-milestone, to confirm nothing was missed.
Retroactively audits a completed phase for security (threat mitigations from the PLAN.md threat model are implemented) and validation (Nyquist test coverage of the phase's requirements). Use after a phase is executed to confirm threats are closed and requirements are tested; runs both audits by default. --security or --validate narrows to one. Open threats block phase advancement.
Scans every phase for outstanding UAT and verification items (pending, skipped, blocked, human-needed), cross-references the codebase to flag stale entries, and produces a prioritized human test plan. Use to find all manual testing still owed across the project.
Based on SOC occupation classification
| name | donny-add-backlog |
| description | Adds an idea to the backlog parking lot using 999.x numbering, kept outside the active phase sequence so it accumulates context without being scheduled. Use when an idea is worth keeping but not ready to plan into the current milestone. |
| argument-hint | <description> |
| allowed-tools | ["Read","Write","Bash"] |
Read ROADMAP.md to find existing backlog entries. Use the Read tool on
.planning/ROADMAP.md (not cat - ROADMAP.md often holds non-ASCII content that
BSD tools treat as binary).
Find next backlog number:
NEXT=$(node "$HOME/.claude/donny/bin/donny-tools.cjs" phase next-decimal 999 --raw)
If no 999.x phases exist, start at 999.1.
Create the phase directory:
SLUG=$(node "$HOME/.claude/donny/bin/donny-tools.cjs" generate-slug "$ARGUMENTS" --raw)
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 /donny-review-backlog when ready)
Commit:
node "$HOME/.claude/donny/bin/donny-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 /donny-discuss-phase {NEXT} to explore it further.
Use /donny-review-backlog to promote items to active milestone.