菜单
Generate or update up to nine project documentation files, each written and fact-checked against the live codebase by subagents. Use when project docs (README, ARCHITECTURE, API, etc.) are missing or stale; pass --verify-only to check accuracy without writing, or --force to regenerate all docs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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.
| name | donny-docs-update |
| description | Generate or update up to nine project documentation files, each written and fact-checked against the live codebase by subagents. Use when project docs (README, ARCHITECTURE, API, etc.) are missing or stale; pass --verify-only to check accuracy without writing, or --force to regenerate all docs. |
| argument-hint | [--force] [--verify-only] |
| allowed-tools | ["Read","Write","Edit","Bash","Glob","Grep","Task","AskUserQuestion"] |
Flag handling rule:
$ARGUMENTS$ARGUMENTS, treat it as inactive--force: skip preservation prompts, regenerate all docs regardless of existing content or Donny markers--verify-only: check existing docs for accuracy against codebase, no generation (full verification requires Phase 4 verifier)--force and --verify-only both appear in $ARGUMENTS, --force takes precedence
<execution_context> @~/.claude/donny/workflows/docs-update.md </execution_context>
Arguments: $ARGUMENTSAvailable optional flags (documentation only - not automatically active):
--force - Regenerate all docs. Overwrites hand-written and Donny docs alike. No preservation prompts.--verify-only - Check existing docs for accuracy against the codebase. No files are written. Reports VERIFY marker count. Full codebase fact-checking requires the donny-doc-verifier agent (Phase 4).Active flags must be derived from $ARGUMENTS:
--force is active only if the literal --force token is present in $ARGUMENTS--verify-only is active only if the literal --verify-only token is present in $ARGUMENTS