AI-assisted enterprise architecture guidance based on TOGAF, Zachman Framework, ADRs, cloud alignment frameworks, and solution architecture patterns.
/plugin install enterprise-architecture@claude-code-pluginsThe "killer app" of this plugin - document and manage architecture decisions.
# Create a new ADR
/ea:adr-management create Use PostgreSQL for persistence
# Explain ADR concepts
/ea:explain ADRWhen to use this vs spec-driven-development:
- Use
/ea:adr-management createfor standalone architecture governance decisions - Use
/spec:adr:create(spec-driven-development plugin) when extracting decisions that emerge during specification authoring
Both use MADR format and can coexist in the same project.
Get phase-specific guidance for TOGAF ADM (Architecture Development Method).
# Get guidance for a specific phase
/ea:togaf-phase A # Architecture Vision
/ea:togaf-phase B # Business Architecture
/ea:togaf-phase preliminary # Preliminary Phase
/ea:togaf-phase requirements # Requirements ManagementAnalyze architecture from specific stakeholder perspectives.
# Analyze from builder perspective (what data structures)
/ea:zachman-analyze builder what
# Use wizard mode
/ea:zachman-analyzeGenerate C4-style architecture documentation.
# Generate different document types
/ea:document context # System context
/ea:document container # Container architecture
/ea:document component # Component details
/ea:document executive-summary # For leadershipComprehensive review against principles and viewpoints.
# Review entire codebase
/ea:architecture-review
# Review staged changes
/ea:architecture-review staged
# Review specific files
/ea:architecture-review src/api/View architecture metrics and status.
/ea:dashboardCheck alignment with cloud frameworks.
# Use the cloud-alignment skill
/ea:explain cloud adoption framework
/ea:explain well-architectedAI-simulated event storming workshops with multi-persona support.
# Full simulation with 5 persona agents debating in parallel
/ea:event-storming "Order fulfillment process" --mode full
# Quick single-pass analysis
/ea:event-storming "Customer onboarding" --mode quick
# Interactive guided session (default)
/ea:event-storming "Payment processing"Modes:
| Mode | Personas | Tokens | Best For |
|---|---|---|---|
full |
5 (parallel) | ~15K | Comprehensive discovery |
quick |
0 | ~3K | Quick domain overview |
guided |
On-demand | Variable | Interactive exploration |
Persona Agents:
- domain-expert: Deep business knowledge, domain events, business rules
- developer-persona: Technical events, integration points, feasibility
- business-analyst: Process flow, commands, actors, acceptance criteria
- product-owner: Priorities, MVP scope, user value
- devils-advocate: Challenges, gaps, contradictions, edge cases
Map relationships between bounded contexts using DDD context mapping patterns.
# Full systematic analysis
/ea:context-mapping bounded-contexts.md --mode full
# Quick obvious patterns only
/ea:context-mapping --mode quick
# Interactive guided session (default)
/ea:context-mappingPatterns Supported:
| Pattern | Abbrev | Description |
|---|---|---|
| Shared Kernel | SK | Shared code/model between contexts |
| Customer/Supplier | C/S | Upstream supplies, downstream consumes |
| Anti-Corruption Layer | ACL | Downstream translates/isolates upstream |
| Open Host Service | OHS | Formal API for consumers |
| Published Language | PL | Standardized API format (OpenAPI, etc.) |
| Conformist | CF | Downstream adopts upstream model |
| Partnership | P | Equal collaboration, mutual dependency |
| Separate Ways | SW | No integration, independent evolution |
Outputs:
- Context Mapper DSL (CML) file for tooling
- Mermaid diagram for visualization
- Team topology alignment suggestions
- Integration strategy recommendations
Capture business processes through pictographic stories.
# Capture current state (AS-IS)
/ea:domain-storytelling "order-fulfillment"
# Capture desired future state (TO-BE)
/ea:domain-storytelling "order-fulfillment" --type to-beOutputs:
- Story sequence diagram (actors, work objects, activities)
- Actor catalog with responsibilities
- Work object catalog with lifecycle
- Bounded context observations
- Glossary of domain terms
Architecture tests for .NET projects.
# Analyze architecture fitness (report only)
/ea:fitness-functions
# Generate NetArchTest tests
/ea:fitness-functions --generate
# Generate ArchUnitNET tests
/ea:fitness-functions --generate --framework archunitnet
# Analyze specific scope
/ea:fitness-functions src/MyModule/ --generateChecks:
- Dependency rules (Domain → Infrastructure violations)
- Layer constraints (Controller placement, DbContext location)
- Naming conventions (Handler, Repository, Controller suffixes)
- Module cross-references (modular monolith boundaries)
Scan code for resilience patterns (Polly, Brighter).
# Basic audit
/ea:resilience-patterns audit
# Detailed audit with code snippets
/ea:resilience-patterns audit --detailed
# Audit specific scope
/ea:resilience-patterns audit src/Infrastructure/Detects:
- HTTP clients without resilience handlers
- Message handlers without retry policies
- Missing circuit breakers
- Missing timeouts
- Dead letter queue gaps
- Anti-patterns (catch-and-swallow, infinite retries)
| Skill | Purpose | Keywords |
|---|---|---|
adr-management |
Create and manage ADRs | adr, decision, alternatives |
ea-learning |
Explain EA concepts | explain, what is, togaf, zachman |
architecture-documentation |
Generate docs with diagrams | document, c4, viewpoint |
togaf-guidance |
TOGAF ADM phase guidance | togaf, adm, phase |
zachman-analysis |
Zachman perspective analysis | zachman, viewpoint, perspective |
gap-analysis |
Current/target state analysis | gap, migration, roadmap |
cloud-alignment |
CAF/Well-Architected alignment | caf, well-architected, azure, aws |
| Skill | Purpose | Keywords |
|---|---|---|
event-storming |
AI-simulated event storming workshops | events, commands, actors, bounded contexts |
context-mapping |
Map bounded context relationships | context map, upstream, downstream, ACL, OHS, CML |
domain-storytelling |
Pictographic domain modeling | stories, actors, work objects, as-is, to-be |
modular-architecture |
Module organization patterns | modules, ports, adapters, hexagonal |
fitness-functions |
Architecture tests for .NET | netarchtest, archunitnet, dependencies |
resilience-patterns |
Polly/Brighter resilience guidance | retry, circuit breaker, dlq, polly, brighter |
| Agent | Purpose | Model |
|---|---|---|
architecture-documenter |
Generate comprehensive docs | Sonnet |
viewpoint-analyzer |
Analyze stakeholder perspectives | Haiku |
principles-validator |
Validate against principles | Sonnet |
migration-explorer |
Explore migration options | Sonnet |
The event-storming-persona agent supports multiple persona types via argument:
| Invocation | Perspective | Model |
|---|---|---|
event-storming-persona domain-expert |
Business knowledge, domain events, rules | Opus |
event-storming-persona developer |
Technical events, integration, feasibility | Opus |
event-storming-persona business-analyst |
Process flow, commands, actors | Opus |
event-storming-persona product-owner |
Priorities, MVP scope, user value | Opus |
event-storming-persona devils-advocate |
Challenges, gaps, contradictions | Opus |
| Agent | Purpose | Model |
|---|---|---|
story-facilitator |
Guide domain storytelling sessions | Opus |
context-mapper |
Map bounded context relationships | Sonnet |
fitness-function-generator |
Generate architecture tests | Opus |
resilience-analyzer |
Audit resilience patterns | Opus |
over-engineering-detector |
Detect unnecessary complexity | Opus |
| Skill | Purpose |
|---|---|
/ea:adr-management <action> [title] |
Create and manage ADRs |
/ea:ea-explain <concept> |
Explain EA concept |
/ea:ea-document <type> |
Generate architecture document |
/ea:togaf-phase <phase> |
Get TOGAF phase guidance |
/ea:zachman-analyze [row] [column] |
Analyze from Zachman perspective |
/ea:architecture-review [scope] |
Review architecture |
/ea:ea-dashboard |
Show architecture metrics |
| Skill | Purpose |
|---|---|
/ea:event-storming <domain> [--mode] |
Run event storming workshop |
/ea:context-mapping [file] [--mode] [--output] |
Map bounded context relationships |
/ea:domain-storytelling <journey> [--type] |
Create domain story |
/ea:fitness-functions [scope] [--generate] |
Analyze architecture fitness |
/ea:resilience-patterns [scope] [--detailed] |
Audit resilience patterns |
The Open Group Architecture Framework provides methodology via the ADM:
- Preliminary Phase + Phases A-H
- Requirements Management (cross-cutting)
- Four domains: Business, Data, Application, Technology
A 6x6 ontology for classifying architecture artifacts:
- Rows: Planner, Owner, Designer, Builder, Subcontractor, User
- Columns: What, How, Where, Who, When, Why
Important: Rows 1-3 require human input; rows 4-6 can be extracted from code.
7 methodologies for Azure adoption:
- Strategy, Plan, Ready, Adopt, Govern, Secure, Manage
6 pillars for workload design:
- Operational Excellence, Security, Reliability
- Performance Efficiency, Cost Optimization, Sustainability
Resilience patterns using the new pipeline API:
.AddStandardResilienceHandler() // Quick setup
.AddResilienceHandler("custom", builder => { // Custom
builder.AddRetry(...)
builder.AddCircuitBreaker(...)
builder.AddTimeout(...)
})Message handler resilience with policy attributes:
[UsePolicy("retry-policy", step: 1)]
[UsePolicy("circuit-breaker", step: 2)]
public override MyCommand Handle(MyCommand command)Architecture fitness functions:
Types.InAssembly(...)
.ShouldNot()
.HaveDependencyOn("Infrastructure")This plugin integrates with the visualization plugin for C4 diagrams:
# Install visualization plugin (recommended)
/plugin install visualization@claude-code-pluginsWhen available, the architecture-documenter agent will generate Mermaid or PlantUML diagrams. Without it, text-based descriptions are provided.
The plugin expects architecture artifacts in /architecture/:
/architecture/
README.md
principles.md
/adr/
0001-initial-architecture.md
0002-database-selection.md
/viewpoints/
context.md
containers.md
/components/
See memory/repository-structure.md for full details.
This plugin acknowledges what it can and cannot do:
- ADR creation and management
- Technology stack analysis (Zachman rows 4-5)
- TOGAF phase guidance
- Code-derived architecture documentation
- Technical gap analysis
- AI-simulated event storming (approximates workshop dynamics)
- Architecture fitness function generation
- Resilience pattern analysis
- Business strategy (Zachman rows 1-2)
- Design rationale (without ADRs)
- Budget and timeline decisions
- Organizational context
- Real stakeholder perspectives (personas simulate, not replace)
All outputs clearly indicate what was extracted from code vs what requires human input.
Reference documentation included:
adr-template.md- Standard ADR formatrepository-structure.md- Directory structure guidetogaf-overview.md- TOGAF 10 quick referencezachman-overview.md- Zachman 3.0 matrixzachman-limitations.md- Code extraction limitsarchitecture-principles.md- Principles templatecloud-frameworks/caf-pillars.md- Microsoft CAFcloud-frameworks/well-architected.md- AWS Well-Architected
This plugin is part of the claude-code-plugins repository. Contributions welcome!
MIT