Guides through TOGAF ADM phases with context-aware advice on activities, deliverables, and enterprise architecture domains. Useful for applying TOGAF methodology or ADM phase work.
npx claudepluginhub melodic-software/claude-code-plugins --plugin enterprise-architectureThis skill is limited to using the following tools:
Use this skill when you need to:
Provides guidance for TOGAF ADM phases (preliminary, A-H, requirements) including purpose, objectives, key activities, deliverables, and connections to other phases. Useful for enterprise architecture development.
Designs enterprise systems using TOGAF framework, ADM phases, capability maps, domain-driven design, and technology transformations. Grounds responses in reference patterns, sharp edges, and validations.
Creates ADRs in MADR format, arc42 documentation, and plan-context.md for architecture proposals. Handles branch verification, GitHub issue/PR creation, artifact triage, and backlog updates.
Share bugs, ideas, or general feedback.
Use this skill when you need to:
Keywords: togaf, adm, architecture development method, phase, business architecture, technology architecture, migration planning, implementation governance, architecture vision
TOGAF (The Open Group Architecture Framework) provides a comprehensive methodology for developing enterprise architecture. The core is the Architecture Development Method (ADM) - an iterative cycle of 10 phases.
| Domain | Focus | Artifacts |
|---|---|---|
| Business | Processes, capabilities, organization | Business process models, capability maps |
| Data | Information assets, data management | Data models, data flow diagrams |
| Application | Applications and their interactions | Application portfolio, integration diagrams |
| Technology | Infrastructure and platforms | Technology standards, deployment diagrams |
Establish the architecture capability within the organization.
Starting a new EA initiative or formalizing existing practices.
Create a high-level vision aligned with strategic goals.
Beginning a new architecture project or major initiative.
Develop the business architecture to support the vision.
Understanding business needs before technical solutions.
Define data and application architectures.
Designing the systems that support business capabilities.
Define the technology infrastructure.
Selecting platforms, infrastructure, and technology standards.
Identify implementation approaches and projects.
Planning how to get from current to target state.
Create detailed implementation roadmap.
Creating the execution plan with timelines and dependencies.
Oversee architecture implementation.
Projects are executing; ensuring they follow the architecture.
Manage changes to the architecture over time.
Maintaining and evolving the established architecture.
Manage architecture requirements throughout all phases.
Note: This is a cross-cutting activity, not a sequential phase. Requirements management operates continuously across all ADM phases.
Not sure which phase you're in? Ask these questions:
You don't need all phases for every project. A minimal cycle:
Follow the full cycle with appropriate rigor:
For detailed phase information, see references/togaf-overview.md.
Date: 2025-12-05 Model: claude-opus-4-5-20251101