This skill should be used when the user asks to "map business capabilities", "build a technology radar", "define architecture governance", "prioritize strategic initiatives", or mentions capability mapping, DDD domains, ARB, DORA metrics, or target operating model. [EXPLICIT] It generates enterprise architecture alignment artifacts including capability maps, domain decomposition, governance frameworks, technology radars, and strategic initiative roadmaps. [EXPLICIT] Use this skill whenever the user needs to align technology initiatives with business strategy, even if they don't explicitly ask for "enterprise architecture". [EXPLICIT]
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdreferences/enterprise-arch-patterns.mdtemplates/output.docx.mdtemplates/output.htmlEnterprise architecture aligns technology initiatives with business strategy. It defines what capabilities the enterprise needs, what technologies support them, how decisions are governed, and how investments are prioritized. [EXPLICIT]
Una empresa sin mapa de capacidades es un ejército sin mapa del terreno. La arquitectura enterprise conecta la estrategia de negocio con la tecnología: qué capacidades necesita la empresa, qué tecnología las soporta, cómo se gobierna, y cómo se prioriza la inversión. Sin esta capa, cada equipo optimiza localmente mientras la empresa se fragmenta.
The user provides an organization or initiative name as $ARGUMENTS. Parse $1 as the enterprise/organization name used throughout all output artifacts. [EXPLICIT]
Parameters:
{MODO}: piloto-auto (default) | desatendido | supervisado | paso-a-paso
{FORMATO}: markdown (default) | html | dual{VARIANTE}: ejecutiva (~40% — S1 capability map + S3 radar + S5 portfolio) | técnica (full 6 sections, default)Before generating architecture, detect organizational context:
!find . -name "*.md" -o -name "*.yaml" -o -name "*.json" | head -20
If reference materials exist, load them:
Read ${CLAUDE_SKILL_DIR}/references/capability-templates.md
Read ${CLAUDE_SKILL_DIR}/references/governance-frameworks.md
Hierarchical decomposition of business capabilities from strategic to operational level. [EXPLICIT]
Structure:
Per capability:
Key outcomes:
Format: Heat map (capability x maturity x color), dependency matrix
Decomposes the enterprise into cohesive domains using Domain-Driven Design principles. [EXPLICIT]
Bounded Contexts:
Context Mapping:
Domain Ownership:
Key decisions:
Guides technology adoption across the enterprise (ThoughtWorks-style). [EXPLICIT]
Classification:
Dimensions: Platforms, Languages, Frameworks, Data, Infrastructure, Architectural Patterns, Security & Compliance
Per technology:
Principles:
Framework for making and enforcing architecture decisions. [EXPLICIT]
Architectural Principles: Long-lived, guide decision-making
Standards & Patterns: API design, logging (structured, correlation IDs), deployment (blue-green, canary), database selection criteria
Architecture Review Board (ARB):
Approval Process:
Compliance & Audit:
Prioritized list of strategic initiatives aligned with business objectives and capability gaps. [EXPLICIT]
Per initiative:
Portfolio Analysis:
Principles:
How the organization is structured and operates to deliver and manage architecture. [EXPLICIT]
Organizational Structure (Team Topologies):
Funding Model: Product funding per capability, platform shared budget, CapEx vs. OpEx
Delivery Cadence: Sprint length, release cadence, ceremonies
Decision Rights: Strategic (CTO), Tactical (ARB), Operational (Teams)
Metrics & Accountability:
| Decision | Enables | Constrains | When to Use |
|---|---|---|---|
| Cloud-First | Scalability, flexibility, innovation speed | Vendor lock-in, compliance complexity, cost | Digital-native orgs, variable workloads |
| Build vs. Buy | Control, differentiation | Higher cost, longer time-to-market | Core domains, competitive advantage |
| Microservices | Independent scaling, tech diversity, autonomy | Ops complexity, distributed debugging | Large teams, high-scale, polyglot |
| Monolithic | Simple operations, single deployment, consistency | Tight coupling, hard to scale independently | Small teams, simple domains |
| Centralized Data Warehouse | Single source of truth, analytics, governance | ETL complexity, latency, tight coupling | Traditional BI, regulatory reporting |
| Decentralized Data Lakes | Agility, quick onboarding, independent optimization | Inconsistency, data quality, governance burden | Data science, exploratory analytics |
| Governance (Heavy) | Control, compliance, consistency | Slow decisions, innovation risk, friction | Regulated industries, large enterprises |
| Governance (Light) | Speed, innovation, team autonomy | Chaos, technical debt, inconsistency | Startups, small teams, fast-moving |
Legacy Enterprise with Technical Debt: Capabilities supported by outdated tech. Modernization competes with new feature development. Prioritize highest-value, lowest-cost improvements; parallel running during transition. [EXPLICIT]
Multi-Geographic or Multi-Regulatory: Different regions have different compliance (GDPR EU, CCPA California). Architecture must accommodate regional customization. Domain model per region, shared kernel for common capabilities. [EXPLICIT]
High-Growth Startup Becoming Enterprise: "Move fast, break things" needs governance. Retrospective capability mapping, gradual governance introduction, strategic initiative prioritization. [EXPLICIT]
Merger or Acquisition: Two enterprises with different architectures, technologies, governance. Capability analysis for synergies, phased integration roadmap, shared platform investments. [EXPLICIT]
Digital Transformation Initiative: High visibility, multiple stakeholders, cross-cutting impact. Clear vision, phased capability evolution, frequent communication, quick wins early. [EXPLICIT]
Before finalizing delivery, verify:
| Format | Default | Description |
|---|---|---|
markdown | Yes | Rich Markdown + Mermaid diagrams. Token-efficient. |
html | On demand | Branded HTML (Design System). Visual impact. |
dual | On demand | Both formats. |
Default output is Markdown with embedded Mermaid diagrams. HTML generation requires explicit {FORMATO}=html parameter. [EXPLICIT]
Primary: A-03_Enterprise_Architecture_Deep.html — Executive summary, capability map, domain model, technology radar, governance framework, initiative portfolio, target operating model.
Secondary: Capability heat map (PNG/SVG), technology radar visualization, strategic roadmap (Gantt), governance flowchart, metrics dashboard.
Author: Javier Montano | Last updated: March 18, 2026
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.