enterprise-architecturelisted

Unified enterprise & software architecture skill grounded in four open-source standards — C4 + Structurizr DSL, ArchiMate 3.x, TOGAF ADM, and arc42 + ADRs (MADR). Use it whenever the user wants to: produce architecture diagrams as code (C4 context/container/component, Structurizr, PlantUML, Mermaid); write architecture docs or decision records (arc42, ADRs/MADRs, design docs); review or assess a design against quality attributes and EA principles; or model an enterprise (capabilities → applications → technology, app landscapes, portfolio rationalization). Trigger it even when no framework is named — e.g. "draw the architecture of this service", "give me a container diagram", "write an ADR for choosing Kafka", "is this design sound?", "map our capabilities to apps", "document my architecture in arc42", "create an HLD or LLD", "assess this design against ISO 25010 / quality attributes", "produce a solution design". Do NOT trigger it for writing application code or REST endpoints, IaC / cloud deployment (Terrafo
gauravs19/enterprise-architecture-skill · ★ 3 · DevOps & Infrastructure · score 69

Install: claude install-skill gauravs19/enterprise-architecture-skill

# Enterprise Architecture A practical toolkit for doing real architecture work the way open-source EA standards intend it — diagrams as code, documentation as code, decisions as records, and a single traceable model underneath. It unifies four complementary frameworks so you reach for the right tool at the right altitude instead of forcing everything into one notation. ## The mental model: four frameworks, four altitudes These frameworks are not competitors — they answer different questions. Knowing which one fits the question is most of the skill. | Framework | Question it answers | Altitude | When to reach for it | |---|---|---|---| | **C4 model** | "How is *this software system* structured?" | System → code | A single system/service: context, containers, components | | **ArchiMate** | "How does the *whole enterprise* hang together?" | Business → app → tech | Capabilities, app landscapes, cross-system flows | | **TOGAF ADM** | "How do we *deliver* an architecture change?" | Process/governance | Running an architecture engagement end-to-end | | **arc42 + ADRs** | "How do we *write it down* so others understand & decisions stick?" | Documentation | Documenting a system; recording a decision | A useful rule of thumb: **C4 zooms into one system, ArchiMate zooms out to the enterprise, TOGAF is the *method* for changing it, and arc42/ADR is how you *narrate* it.** They compose: an arc42 doc embeds C4 diagrams and links ADRs; a TOGAF engagement produces ArchiMate models and A