loom-codebase-atlaslisted

# loom-codebase-atlas Codebase atlas is a zoom-out playbook. It maps a relevant code area in terms of domain language, modules, callers, interfaces, and decisions, then records accepted reusable context in knowledge. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-knowledge`, `loom-research`, `loom-constitution`, `loom-specs`, `loom-evidence`, and `loom-tickets`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. It explains the codebase. It does not replace specs, tickets, evidence, or audit. ## Use This Playbook When Use this playbook when: - the agent is unfamiliar with a code area - a ticket needs context before safe execution - a bug or review requires caller/callee understanding - a plan depends on module relationships - architecture terms need grounding in actual code - a future agent would benefit from a persistent map Skip it when a narrow file read is enough to complete a small scoped edit safely. ## Route Use this route: ```text question -> scope -> map -> explain -> record -> route ``` ## Question Start with the reason for the atlas. Examples: - Where does this behavior enter the system? - Which modules call this interface? - What owns this data lifecycle? - Which code paths must a worker understand before editing? - Why does this area feel tangled? The atlas should answer a retrieval need, not become a full repository tour.