메뉴
Single-terminal command center for a milestone: a live dashboard of every phase with status, recommended next actions, and dispatch (discuss runs inline, plan and execute run as background agents). Use when driving or parallelizing work across many phases from one terminal instead of running phase commands one at a time.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | donny-manager |
| description | Single-terminal command center for a milestone: a live dashboard of every phase with status, recommended next actions, and dispatch (discuss runs inline, plan and execute run as background agents). Use when driving or parallelizing work across many phases from one terminal instead of running phase commands one at a time. |
| allowed-tools | ["Read","Write","Bash","Glob","Grep","AskUserQuestion","Skill","Task"] |
Designed for power users who want to parallelize work across phases from one terminal: discuss a phase while another plans or executes in the background.
Creates/Updates:
.planning/STATE.md, .planning/ROADMAP.md, phase directories for status.After: User exits when done managing, or all phases complete and milestone lifecycle is suggested.
<execution_context>
@/.claude/donny/workflows/manager.md
@/.claude/donny/references/ui-brand.md
</execution_context>
Project context, phase list, dependencies, and recommendations are resolved inside the workflow using donny-tools.cjs init manager. No upfront context loading needed.
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.