enterprise-architecture

PROACTIVELY use when generating architecture documentation. Analyzes codebase, identifies components, generates comprehensive docs with C4 diagrams.

Analyzes bounded contexts and maps relationships using DDD context mapping patterns. PROACTIVELY use after event storming when bounded contexts are identified and integration strategies need to be defined. Produces Context Mapper DSL (CML) output with upstream/downstream relationships, integration patterns (ACL, OHS, SK), and team topology suggestions.

PROACTIVELY use during event storming workshops to simulate various perspectives. Supports persona types: business-analyst, developer, devils-advocate, domain-expert, product-owner. Pass persona type as argument.

PROACTIVELY use when generating architecture tests for .NET projects. Creates NetArchTest or ArchUnitNET fitness functions that enforce architectural decisions and module boundaries.

PROACTIVELY use when exploring technical migration paths. Documents current state, identifies options with trade-offs - explores rather than prescribes strategies.

PROACTIVELY use when reviewing code for unnecessary complexity. Detects over-engineering, speculative generality, and identifies when simpler solutions would suffice.

PROACTIVELY use when validating code changes against architecture principles. Checks alignment, reports violations with severity, suggests remediation.

PROACTIVELY use when auditing code for resilience patterns. Analyzes retry, circuit breaker, and error handling - identifies gaps and suggests Polly/Brighter improvements.

PROACTIVELY use when facilitating domain storytelling sessions. Captures actors, work objects, activities, and story sequences to create structured AS-IS and TO-BE story artifacts.

PROACTIVELY use when analyzing architecture from stakeholder viewpoints. Handles Zachman row/column perspectives with honest limitations for rows 1-3.

Create and manage Architecture Decision Records (ADRs). Use when documenting technology choices, design decisions, or architectural changes that need to be tracked over time. This is the CANONICAL ADR skill - all ADR-related work should use this skill.

Generate architecture documents using templates with diagram integration. Use for creating C4 diagrams, viewpoint documents, and technical overviews.

Review architecture of current codebase or staged changes

Align with cloud architecture frameworks (Microsoft CAF, AWS Well-Architected). Check alignment with pillars, identify gaps.

Map relationships between bounded contexts using DDD context mapping patterns. Use when defining upstream/downstream relationships, integration strategies (ACL, OHS, PL), or generating Context Mapper DSL output. Follows event storming for bounded context discovery.

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

Collaborative domain modeling through pictographic stories. Use when gathering requirements, understanding business workflows, onboarding team members, or preparing for event storming. Follows Stefan Hofer & Henning Schwentner's methodology with actors, work objects, and activities.

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

Explain enterprise architecture concepts in practical terms. Use when learning about TOGAF, Zachman, ADRs, or any EA terminology.

AI-simulated event storming workshop with multi-persona support. Use when discovering domain events, commands, actors, and bounded contexts. Supports three modes - full-simulation (5 persona agents debate), quick (single-pass analysis), and guided (interactive with user). Orchestrates persona agents and synthesizes results.

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

Architecture test guidance for .NET using NetArchTest and ArchUnitNET. Use when enforcing architectural boundaries, testing module dependencies, validating layer constraints, or creating performance fitness functions. Includes code generation templates.

Compare current state to target state architecture. Scoped to technical options - requires business context for complete analysis.

Module organization patterns including ports and adapters (hexagonal), module communication, and data isolation. Use when structuring modular monoliths, defining module boundaries, setting up inter-module communication, or isolating database contexts. Includes MediatR patterns for internal events.

Circuit breaker, retry, and DLQ patterns for .NET using Polly and Brighter. Use when implementing fault tolerance, handling transient failures, configuring retry strategies, or setting up dead letter queues. Includes Polly HttpClient patterns and Brighter message handler resilience.

Team Topologies methodology for organizational design. Covers the four fundamental team types, three interaction modes, cognitive load assessment, Inverse Conway Maneuver, and team evolution patterns. Use when designing team structures that align with architecture.

Guide users through TOGAF ADM phases with context-aware advice. Use when applying TOGAF methodology or understanding ADM phase activities.

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

Wardley Mapping for strategic positioning and situational awareness. Covers value chain mapping, evolution stages, landscape analysis, gameplay patterns, and strategic decision-making. Use for technology strategy, competitive analysis, and architectural investment decisions.

Apply Zachman Framework perspective analysis with honest limitations. Analyze architecture from specific row/column perspectives.

Analyze from Zachman perspective (row: planner/owner/designer/builder/subcontractor/user, column: what/how/where/who/when/why)