Menu
Use when generating or maintaining codebase documentation. Divio framework.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | codebase-documentation |
| description | Use when generating or maintaining codebase documentation. Divio framework. |
| version | 1.0.0 |
| tags | ["docs","authoring"] |
∀ codebase analysis tasks. ∀ documentation tasks.
| Type | Purpose | Audience | Style |
|---|---|---|---|
| Tutorial | Learning-oriented | New dev | Step-by-step, "do this, then this" |
| How-to | Task-oriented | Working dev | "To achieve X, do Y" |
| Reference | Information-oriented | Any dev | Accurate, complete, terse |
| Explanation | Understanding-oriented | Curious dev | Discursive, "why" focused |
| File | Focus | Content |
|---|---|---|
| STACK.md | Technology | Languages, frameworks, tools, versions, rationale |
| ARCHITECTURE.md | Structure | Patterns, layers, boundaries, data flow |
| CONCERNS.md | Cross-cutting | Tech debt, security, fragile areas, missing coverage |
| CONVENTIONS.md | Standards | Naming, file structure, commit format, review process |
project docs directory (e.g., docs/)Use when reviewing architecture decisions. C4 model, dependency inversion, hexagonal boundaries.
Use during discuss-slice and plan-slice to stress-test a spec or plan against domain vocabulary before approval.
Use during research-slice to build disposable experiments that answer technical uncertainty.
Use during project:init to scaffold repo-level agent configuration (CLAUDE.md, AGENTS.md, tracker labels).
Use when debugging. 4-phase investigation, root cause, minimal fix.
Use when implementing features/fixes. Iron law: ¬∃ production code without failing test.