メニュー
Use at feature start (or when the map is stale) to map the repo's structure ONCE into docs/codebase-map.md — a token-lean, depth-limited structural map that plan-writer, analyze, and implement-feature reuse instead of re-exploring the tree each phase.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | codebase-map |
| description | Use at feature start (or when the map is stale) to map the repo's structure ONCE into docs/codebase-map.md — a token-lean, depth-limited structural map that plan-writer, analyze, and implement-feature reuse instead of re-exploring the tree each phase. |
When: at the start of a non-trivial feature/refactor, before or during plan-writer, in a repo the current session has not already mapped — or when docs/codebase-map.md exists but the structure has drifted (new top-level modules, moved boundaries). Skip on a repo small enough to hold in head, or when a fresh map already exists this session. Companion skill, not a forced chain link.
Template: none — produces a generated artifact, not a filled template.
Output: docs/codebase-map.md — a living artifact. Seed once, then refresh in place; never a per-feature file. Token-lean by design: it is read many times (every downstream phase), so it favors a scannable map over prose.
Steps:
docs/codebase-map.md exists and the structure has not drifted, stop — reuse it. Do not regenerate for cosmetic reasons.node_modules, dist, build, .git, vendored deps, or generated output). Prefer one broad Explore/Glob fan-out over reading whole files — locate structure, don't audit code.naming-conventions/postgres-conventions when the stack-conventions pack is installed).TODO/uncertain rather than inventing.docs/codebase-map.md. Record the commit/date it reflects at the top so drift is detectable later.Next: plan-writer reads docs/codebase-map.md to ground Arquitetura / Estrutura de Arquivos in the real structure; analyze and implement-feature reuse it. Regenerate when the structure drifts, not per feature.
Ingest a raw source into the project's OKF knowledge bundle — distill it into concept pages, refresh the index, and log the change. keel's compounding "LLM wiki" loop.
Use when implementation is complete, gates pass, and you need to decide how to integrate the work — presents structured options (merge, PR, keep, discard) and handles the chosen workflow, including worktree cleanup. Closes the SDD cycle after review-and-simplify.
Use when executing implementation plans with independent tasks in the current session
Orchestrates the implement-feature, evaluator, fix-runner loop for the active feature until all Criterios de Aceitacao are met and quality gates are green.
Use after the plan is approved to break the active feature's plan into a concrete task checklist, written into specs/<feature>/tasks.md from the tasks template.
Use while implementing a feature that has retries, queues, background jobs, external calls, or any critical path an on-call engineer will need to reason about in production. Invoke when adding a new endpoint, dependency, or async flow, and before considering such a feature done — instrumentation is developed alongside the code, like tests, not bolted on after.