enterprise-architecture

Create a new Architecture Decision Record (ADR). Use when documenting significant architecture decisions, technology choices, or design patterns that affect the system.

Review architecture of current codebase or staged changes

Map relationships between bounded contexts using DDD context mapping patterns. Typically follows event storming to define integration strategies between discovered contexts.

Detect unnecessary complexity, speculative generality, and over-engineered solutions in code

Create domain stories using pictographic storytelling. Captures actors, work objects, activities, sequences. Outputs AS-IS or TO-BE stories.

Show architecture overview and metrics (ADR count, documentation coverage, Zachman cell coverage)

Generate architecture document (context, container, component, deployment, data, executive-summary)

Explain an enterprise architecture concept

Run AI-simulated event storming workshop. Modes - full (5 personas), quick (single pass), guided (interactive). Discovers domain events, commands, actors, bounded contexts.

Explore migration paths when planning architecture changes. Documents current state, identifies options with trade-offs for informed decision-making.

Analyze architecture fitness and optionally generate architecture tests.

Audit codebase for resilience patterns and identify gaps in fault tolerance.

Get guidance for TOGAF ADM phase (preliminary, A-H, requirements)

Analyze architecture from a specific Zachman Framework perspective.