菜单
Analyze an existing codebase with parallel mapper agents to produce seven structured .planning/codebase/ documents (stack, architecture, structure, conventions, testing, integrations, concerns). Use on a brownfield project before planning, or to refresh the codebase map after major changes; pass an optional focus area.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | donny-map-codebase |
| description | Analyze an existing codebase with parallel mapper agents to produce seven structured .planning/codebase/ documents (stack, architecture, structure, conventions, testing, integrations, concerns). Use on a brownfield project before planning, or to refresh the codebase map after major changes; pass an optional focus area. |
| argument-hint | [optional: specific area to map, e.g., 'api' or 'auth'] |
| allowed-tools | ["Read","Bash","Glob","Grep","Write","Task"] |
Each mapper agent explores a focus area and writes documents directly to .planning/codebase/. The orchestrator only receives confirmations, keeping context usage minimal.
Output: .planning/codebase/ folder with 7 structured documents about the codebase state.
<execution_context> @~/.claude/donny/workflows/map-codebase.md </execution_context>
Focus area: $ARGUMENTS (optional - if provided, tells agents to focus on specific subsystem)Load project state if exists: Check for .planning/STATE.md - loads context if project already initialized
This command can run:
<when_to_use> Use map-codebase for:
Skip map-codebase for:
<success_criteria>
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.
