enterprise-architecture_skill

Overview

This skill helps design and validate enterprise architectures using TOGAF, capability maps, domain-driven design, and technology transformation planning. It focuses on ADM phases, architecture domains, and governance to produce actionable artifacts and risk-aware plans. Use it for creating, diagnosing, and reviewing architectures with strict reference-driven guidance.

How this skill works

When creating artifacts, the skill consults the reference patterns to ensure outputs follow established construction rules and reusable templates. For diagnosis it uses the sharp edges reference to identify likely failure modes and explain root causes and risk impacts. During reviews it applies the validations reference to run objective checks against constraints and provide clear remediation steps.

When to use it

• Designing a target state architecture aligned to business capabilities and TOGAF ADM phases
• Creating capability maps, context maps, domain models, or bounded contexts for DDD
• Planning technology transformations, migrations, or incremental modernization waves
• Assessing architecture governance, principles, and compliance before approvals
• Diagnosing recurring integration, performance, or ownership failures in a system

Best practices

• Always ground designs in the reference patterns file to ensure consistency and repeatability
• Use capability maps to connect business outcomes to architectural scope and priorities
• Model bounded contexts and domain boundaries early to reduce integration friction
• Validate artifacts against the validations reference before stakeholder reviews
• Document identified risks using sharp edges guidance and include clear mitigation owners

Example use cases

• Produce a TOGAF-aligned roadmap across ADM phases with prioritized workstreams and governance checkpoints
• Create a capability map that maps business capabilities to systems, data domains, and teams
• Define bounded contexts and event contracts to enable safe domain-driven decompositions
• Assess a proposed cloud migration plan for architectural risks and non-compliance against validations
• Diagnose an integration failure pattern and recommend targeted fixes with root-cause explanation