Stats
Actions
Tags
Explains enterprise architecture concepts like TOGAF, Zachman, ADRs, C4 Model, and principles in practical developer terms. Useful for learning EA terminology and linking to codebases.
How this skill is triggered — by the user, by Claude, or both
Slash command
/enterprise-architecture:ea-learningThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when you need to:
Use this skill when you need to:
Keywords: explain, what is, why, learn, togaf, zachman, enterprise architecture, adm, viewpoint, stakeholder, architecture principle
This skill provides practical, developer-focused explanations that:
Not sure where to start? Use these practical entry points:
| If you want to... | Start with... |
|---|---|
| Document a decision | ADR (Architecture Decision Record) |
| Understand system structure | C4 Model diagrams |
| Plan a migration | Gap Analysis |
| Communicate to executives | Stakeholder Viewpoints |
| Ensure design consistency | Architecture Principles |
What: A document capturing a significant design decision and its context.
Why: Decisions get forgotten. New team members don't know why things were built a certain way. ADRs preserve institutional knowledge.
When to use: Any decision that affects multiple components, is hard to reverse, or involves trade-offs.
What: A comprehensive methodology for developing enterprise architecture.
Why: Provides structured approach to large-scale architecture work with governance and stakeholder management.
Key concept: The ADM (Architecture Development Method) - a cycle of phases from vision through implementation.
What: A 6x6 classification matrix for organizing architecture artifacts.
Why: Ensures complete coverage - every perspective (who, what, how, when, where, why) is documented for every stakeholder level.
Key insight: It's a taxonomy (how to organize), not a methodology (how to create).
What: A hierarchical approach to software architecture diagrams.
Why: Provides consistent abstraction levels (Context, Container, Component, Code) that communicate clearly to different audiences.
Levels:
What: Foundational rules that guide design decisions.
Why: Ensure consistency across teams and decisions. Provide guardrails without micromanagement.
Format: Statement + Rationale + Implications
When explaining concepts, this skill will:
| Question | Answer |
|---|---|
| Do I need TOGAF certification to use EA concepts? | No. The concepts are valuable regardless of certification. Start with ADRs and principles. |
| Is Zachman too heavyweight for my project? | Use it as a checklist, not a requirement. Even checking 2-3 cells improves coverage. |
| How do EA frameworks relate to agile? | EA provides "just enough" architecture upfront. Decisions evolve through ADRs. |
| What's the minimum viable EA? | ADRs + Architecture Principles + C4 Context Diagram. You can build from there. |
For detailed framework information, see:
references/togaf-overview.md - TOGAF 10 ADM phasesreferences/zachman-overview.md - Zachman 3.0 matrixreferences/architecture-principles.md - Principles templateDate: 2025-12-05 Model: claude-opus-4-5-20251101
npx claudepluginhub melodic-software/claude-code-plugins --plugin enterprise-architectureExplains enterprise architecture concepts like TOGAF, ADR, Zachman Framework, and landing zones in practical terms for developers and architects with examples and links.
Guides system design, architecture reviews, ADR creation, hexagonal compliance, Mermaid/PlantUML diagram generation, and layer dependency enforcement.
Designs, reviews, and documents complex software architectures using C4 Mermaid diagrams, ADRs, and patterns like Clean, Hexagonal, and DDD for system design reviews.