What problem does it solve? Multi-repo agent workflows suffer from duplicated logic and unclear ownership when no canonical map defines which repo owns what. This Skill maintains the ADR-001 INTENT layer: a curated RACI plus C4 component map that records lane ownership, exposed contracts, and forbidden cross-lane imports before teams are dispatched. ## Core Features & Use Cases - Template Seeding: Copies the raci-component-map.md template into docs/architecture/ when the map does not yet exist, so curation starts from a structured baseline. - Lane-Rules Audit: Parses .cto/projects.yaml and reports which registered repos have a lane-rules.txt declaring their forbidden imports. - Diagram Rendering: Regenerates the Mermaid component diagram from the curated RACI rows, keeping the visual map in sync with ownership decisions. - Use Case: Before decomposing a feature across three repos, run the skill to confirm each repo's lane, check which cross-lane imports are forbidden, and prevent two teams from building the same logic. ## Quick Start Ask the agent to run the arch-map skill to seed and render the RACI component map for the registered repos.