enterprise-architecture — a Claude Code Agent Skill

A unified enterprise & software architecture skill for Claude Code, grounded in four open-source standards instead of one. It helps Claude produce architecture work the way the standards intend it: diagrams as code, documentation as code, decisions as records, and one traceable model underneath.

🌐 Live site & eval examples: https://gauravs19.github.io/enterprise-architecture-skill/

Framework	Answers	Used for
C4 model + Structurizr DSL	"How is this system built?"	Context / Container / Component diagrams
ArchiMate 3.x	"How does the enterprise fit together?"	Capabilities → apps → technology
TOGAF ADM	"How do we deliver the change?"	Engagement structure, roadmaps, portfolio
arc42 + ADR/MADR	"How do we write it down?"	System docs & decision records

---

Contents

• Why this exists
• The theory — frameworks in practice
• The mental model — four frameworks, four altitudes
• The four frameworks
• The four modes
• Traceability — one model under everything
• Install
• Usage
• The consistency linter
• Eval results
• Repository layout
• License

---

Why this exists

The open-source ecosystem has excellent single-purpose skills — C4+ArchiMate plugins, arc42 toolkits, ADR generators — but none unify all four frameworks, and none cover TOGAF or architecture review. This skill fills that gap: one skill that picks the right framework at the right altitude, produces everything as code, and keeps a single traceable model under every diagram, doc, and decision.

The theory — frameworks in practice

There's a large gap between how EA frameworks are marketed and how they're used. Almost no organization runs TOGAF or Zachman "by the book" — full-ceremony adoption usually collapses under its own weight. What survives contact with reality is selective borrowing:

Framework	What practitioners actually keep
Zachman	The mental model (what/how/where/who/when/why × audience), not the 36-cell grid. A 30-minute lens, not a study project.
TOGAF	ADM as a scoping checklist; Baseline → Target → Gap → Roadmap as the transformation backbone; the governance vocabulary (ARB, principles, waivers).
FEAF / DoDAF	Only if you sell into government/defense — the RFP will name them.
Capability maps (BIZBOK)	Probably the most-used single EA artifact in real life — the one page executives actually read.
C4 / ArchiMate / arc42 + ADRs	Where the hands-on value lives — this skill's four. arc42 + ADRs have the best value-to-ceremony ratio in the whole space.

Where frameworks genuinely earn their keep: M&A integration (two of everything — what to kill?), cloud migration programs (baseline/target/gap keeps multi-year work coherent), vendor/platform decisions (ADRs make them defensible two years later), regulatory traceability (requirement → capability → app → deployment), and fighting shadow-IT sprawl (a maintained app landscape is the only way anyone knows what exists).