arch-map

Seeds and renders the RACI component map with Mermaid diagrams for multi-repo ownership boundaries.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/apireno/agent-workflow-template --skill arch-map-apireno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch-map
Source: https://github.com/apireno/agent-workflow-template/tree/main/.claude/skills/arch-map
Command: npx skills add https://github.com/apireno/agent-workflow-template --skill arch-map-apireno

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about arch-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a RACI component map for multiple repos?▼

Run the arch-map skill, which copies the raci-component-map.md template into docs/architecture/ if missing. Then curate one row per repo covering its lane, owned contracts, and forbidden cross-lane imports, and re-render the Mermaid diagram.

How do I check which repos are missing lane-rules files?▼

The skill parses .cto/projects.yaml and prints a checklist marking each active repo with [x] if docs/architecture/lane-rules.txt exists or [ ] if forbidden imports are not yet declared.

Does this skill generate detailed UML class diagrams?▼

No. Detailed per-repo UML is delegated to VP-Eng, which derives diagrams from the code AST, and fleet-wide derived UML comes from the code-graph engine via /codegram. This skill only maintains the hand-curated INTENT layer.

What happens if the architecture template file is missing?▼

The script prints an error stating the template docs/architecture/_templates/raci-component-map.md is missing and does not create the map. You must restore the template before seeding can proceed.

When should I consult the RACI map during development?▼

Consult it at decomposition time, before firing dev teams, to verify ownership boundaries and prevent duplicated logic or lane drift across repos. It is ADR-gated, so ownership changes go through architecture decision records.