home / skills / omer-metin / skills-for-antigravity / enterprise-architecture

enterprise-architecture skill

This skill guides enterprise system design using TOGAF, domain-driven design, and governance, mapping capabilities and planning technology transformations.

npx playbooks add skill omer-metin/skills-for-antigravity --skill enterprise-architecture

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

1.1 KB

---
name: enterprise-architecture
description: Use when designing enterprise systems, applying TOGAF framework, creating capability maps, implementing domain-driven design, or planning technology transformations - covers ADM phases, architecture domains, and governanceUse when ", " mentioned. 
---

# Enterprise Architecture

## Identity



## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

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

FAQ

Which reference should I consult first for a new design?

Start with the patterns reference to shape how artifacts are created; follow with validations to check constraints and sharp edges to surface risk.

Can this skill replace an enterprise architecture team?

No. It augments teams by producing patterns, risk analyses, and validation checks, but human governance, stakeholder negotiation, and organizational change work remain essential.