# enterprise-architecture: Connect enterprise change to capabilities and decisions

## Why Install This Skill

Enterprise initiatives often fail because capabilities, applications, operating
responsibilities, and investments are described in separate conversations. This
skill helps an agent create a coherent view of what the organization can do, what
supports it today, what should change, and which decisions must be made along the
way.

It is useful when a portfolio contains duplicated applications, when a target
architecture is too distant to adopt directly, or when architecture governance is
either a bottleneck or too vague to resolve conflicts. The output is designed to be
used by executives, domain owners, product leaders, architects, and delivery teams.

## What You Get

| Path | Purpose |
|---|---|
| `SKILL.md` | Workflow, output contract, and ownership routing |
| `references/` | Focused methods for mapping, states, operating models, governance, and engagement |
| `templates/` | Fillable context brief, portfolio view, and transition roadmap |
| `evals/evals.json` | Nine output-quality cases, including boundary and near-miss routing |

## Quick Start

Ask for a concrete artifact, for example:

```text
Map the capabilities and applications involved in our claims intake modernization,
show duplication and ownership gaps, and propose a transition sequence.
```

Expect a decision-oriented result with evidence, assumptions, owners, dependencies,
and explicit handoffs rather than a generic framework summary.

## Triggers

- Enterprise capability or value-stream mapping
- Application, information, or technology portfolio alignment
- Current, target, or transition architecture across domains
- Enterprise architecture operating model or architecture roles
- Federated architecture governance and decision rights
- Architecture stakeholder engagement or accessible architecture information

## Requirements

- No runtime dependencies or API keys
- Access to the organization's portfolio, ownership, strategy, and delivery evidence improves results
- Specialist skills may be needed for system design, data, APIs, organization design, product roadmaps, technology posture, or corporate strategy