メニュー
Enterprise architecture patterns following TOGAF ADM methodology. Implements capability-driven design, federated architecture, and technology-agnostic specifications. Activates for enterprise-scale architecture decisions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Backend-for-Frontend architecture patterns for API aggregation, data transformation, and client-specific optimization. Activates when designing API layers between backends and frontends or implementing data transformation pipelines.
Generates and maintains codebase context documentation (.context.md files). Implements the Codebase Context Specification for AI-friendly project documentation. Activates when documenting architecture or onboarding.
Three-phase task execution framework with refinement strategies and role-specific prompting. Automatically activates when designing prompts, optimizing task flows, or implementing iterative improvement patterns.
Implements Adversarial Agile Processes (AAP) for document and code review. Challenges assumptions, questions decisions, and suggests improvements. Use when reviewing PRs, documentation, or architectural decisions.
Comprehensive skill for working with Agile Protocol Specification documentation. Automatically activates when creating, editing, or reviewing APS content. Provides templates, naming conventions, and document lifecycle guidance.
SOC 職業分類に基づく
| name | togaf-architecture |
| description | Enterprise architecture patterns following TOGAF ADM methodology. Implements capability-driven design, federated architecture, and technology-agnostic specifications. Activates for enterprise-scale architecture decisions. |
| allowed-tools | ["Read","Write","Edit","Glob"] |
This skill implements enterprise architecture patterns based on the TOGAF Architecture Development Method (ADM).
Focus on capabilities, not specific tools:
Define systems by what they accomplish:
capabilities:
- Business Process Automation
- Real-Time Decision Making
- Multi-Cloud Interoperability
- AI Integration
- Compliance Management
All components should be:
Specifications should survive technology changes:
phase: vision
objectives:
- Define business capability
- Identify stakeholders
- Establish success metrics
- Create architecture vision
deliverables:
- Architecture vision document
- Stakeholder analysis
- Business requirements
phase: business
objectives:
- Map business processes
- Define organizational structure
- Identify information flows
- Document business services
deliverables:
- Business process models
- Organization charts
- Information flow diagrams
phase: information-systems
objectives:
- Data architecture design
- Application architecture design
- Integration architecture
deliverables:
- Data models
- Application portfolio
- Integration patterns
phase: technology
objectives:
- Infrastructure design
- Platform selection
- Security architecture
- Operations design
deliverables:
- Infrastructure diagrams
- Technology standards
- Security controls
---
module-name: [Enterprise Module Name]
version: [X.Y.Z]
description: |
[Description aligned with enterprise architecture goals]
principles:
- Flexibility and Agility
- Scalability
- Resilience
- Security by Design
- Data-Driven
capabilities:
- [Capability 1]
- [Capability 2]
directives:
- Use TOGAF's ADM for continuous alignment
- Implement capability-based approach
- Ensure modular, loosely-coupled services
- Apply enterprise-wide monitoring
architecture:
style: Federated with Event-Driven Capabilities
components:
- [Component 1]
- [Component 2]
data-flow:
- Business Process → Data Capture → Analysis → Compliance → Outcome
business-requirements:
key-features:
- [Feature 1]
- [Feature 2]
target-audience: [Stakeholders]
success-metrics:
- [99.99% uptime]
- [100% compliance]
quality-assurance:
testing-frameworks:
- Chaos Engineering
- Performance Testing
- Security Testing
coverage-threshold: 100% auditability
performance-benchmarks:
- Sub-second latency
- 30-second disaster recovery
deployment:
platform: Multi-Cloud Interoperability
cicd-pipeline: DevSecOps with Policy as Code
---
Central Governance
|
+---+---+
| |
Domain A Domain B
| |
Services Services
Producer → Event Bus → Consumer(s)
↓
Event Store
Capability: Payment Processing
↓
Interfaces: REST API, Event Streams
↓
Implementation: [Any technology that fulfills interface]