codebase-suitelisted

# Codebase Suite Gives an agent a solid understanding of an unfamiliar codebase — structured, traceable, without uncontrolled changes — and produces maintainable project documentation from it. ## Goal Instead of diving into a foreign codebase in an unstructured way, this skill runs through a clearly paced process: - Capture the project context - Inventory the technical foundation - Understand features and structure - Assess risks and technical debt - Create documentation - Prepare the repository structure - Plan and prioritize the implementation - Later: re-verify the documentation against the evolved code and update it The result: - **`_docs/`** — durable technical documentation suitable for both humans and agents (`architecture.md`, `important-files.md`, `setup.md`, `database.md`, `deployment.md`, `api.md`, `workflows.md`, `known-issues.md`). Plus **`_docs/TODO.md`** as the central, curated overview of open tasks that points to the detailed sources (e.g. `known-issues.md`, `_docs/intake/`). - **`_docs/intake/`** — versionable analysis and process artifacts (context, inventory, risk, roadmap, implementation plan). These go stale faster than `_docs/`, so they are deliberately kept separate. - **Optional `CLAUDE.md` + `AGENTS.md`** — when the documentation should be provided to AI agents. `AGENTS.md` carries the docs index, `CLAUDE.md` only points to it. - **`_docs/intake/run-log.md`** — one line per suite run (date, mode, commit) so later runs know what state the docume