Menu
Reviews every 999.x backlog item one by one and promotes, keeps, or removes each. Use when clearing the backlog parking lot into the active milestone, typically before starting or planning a new 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.
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.
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.
Based on SOC occupation classification
| name | donny-review-backlog |
| description | Reviews every 999.x backlog item one by one and promotes, keeps, or removes each. Use when clearing the backlog parking lot into the active milestone, typically before starting or planning a new milestone. |
| allowed-tools | ["Read","Write","Bash","AskUserQuestion"] |
List backlog items:
ls -d .planning/phases/999* 2>/dev/null || echo "No backlog items found"
Read ROADMAP.md and extract all 999.x phase entries. Use the Read tool on
.planning/ROADMAP.md (not cat - it often holds non-ASCII content BSD tools treat as binary).
Show each backlog item with its description, any accumulated context (CONTEXT.md, RESEARCH.md), and creation date.
Present the list to the user via AskUserQuestion:
For items to PROMOTE:
NEW_NUM=$(node "$HOME/.claude/donny/bin/donny-tools.cjs" phase add "${DESCRIPTION}" --raw)
NEW_SLUG=$(node "$HOME/.claude/donny/bin/donny-tools.cjs" generate-slug "${DESCRIPTION}" --raw)
git mv ".planning/phases/${OLD_DIR}" ".planning/phases/${NEW_NUM}-${NEW_SLUG}" 2>/dev/null \
|| mv ".planning/phases/${OLD_DIR}" ".planning/phases/${NEW_NUM}-${NEW_SLUG}"
## Backlog to the active phase list(BACKLOG) marker**Depends on:** fieldFor items to REMOVE:
## Backlog sectionCommit changes:
node "$HOME/.claude/donny/bin/donny-tools.cjs" commit "docs: review backlog - promoted N, removed M" --files .planning/ROADMAP.md
Report summary:
## Backlog review complete
Promoted: {list of promoted items with new phase numbers}
Kept: {list of items remaining in backlog}
Removed: {list of deleted items}