workflow-codebase-knowledgelisted

# Workflow: Codebase Knowledge **Announce at start:** "Activating `swe-workbench:workflow-codebase-knowledge` to present a structured knowledge document." ## When to invoke - Onboarding to an unfamiliar codebase: "walk me through this repo." - Knowledge-handoff request: "give the incoming engineer a mental model of the service." - Reviewer context-gathering: "what are the public API surfaces before I start the PR review?" - Architecture exploration: "show me the module boundaries and their relationships." ## When NOT to invoke - **Defect detection or ranked findings** → use `swe-workbench:workflow-codebase-audit` (cold-start multi-axis sweep with reasoning chains and severity ranking). - **Generating new prose documentation** (READMEs, ADRs, ARCHITECTURE files) → use `/swe-workbench:document` which delegates to the `swe-workbench:tech-writer` subagent. - **Known bug with a repro** → use `/swe-workbench:debug`. - **PR diff review** → use `/swe-workbench:review`. ## Composition Read-only sweep — no subagents dispatched. May delegate file discovery to `Explore` agents in parallel for breadth when the path scope is wide. Never writes to disk. ## Path argument An optional path narrows the scope: `/swe-workbench:codebase-knowledge src/` focuses all phases on `src/` and its descendants. Without a path, the sweep covers the entire repo root. A token is treated as a path if it contains `/`, starts with `.`, or matches an existing directory in the repo; otherwise the entire a