Vibeship-spawner-skills enterprise-architecture

id: enterprise-architecture name: Enterprise Architecture category: enterprise 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 governance

patterns: golden_rules: - rule: "Architecture serves business" reason: "Technology for its own sake fails" - rule: "Iterate, don't waterfall" reason: "Big-bang transformations rarely work" - rule: "Govern, don't gatekeep" reason: "Enable teams while ensuring alignment" - rule: "Document decisions" reason: "Future architects need context" - rule: "Measure outcomes" reason: "Architecture must prove value"

togaf_adm: preliminary: "Framework and principles" phase_a: "Architecture Vision" phase_b: "Business Architecture" phase_c: "Information Systems Architecture" phase_d: "Technology Architecture" phase_e: "Opportunities and Solutions" phase_f: "Migration Planning" phase_g: "Implementation Governance" phase_h: "Architecture Change Management" center: "Requirements Management"

architecture_domains: business: artifacts: - "Business Capability Map" - "Value Stream Map" - "Business Process Models (BPMN)" stakeholders: ["CEO", "COO", "Business Unit Leads"] data: artifacts: - "Conceptual Data Model" - "Logical Data Model" - "Data Dictionary" stakeholders: ["CDO", "Data Stewards", "DBA"] application: artifacts: - "Application Portfolio" - "Service Catalog" - "API Specifications" stakeholders: ["CIO", "Application Owners", "Developers"] technology: artifacts: - "Infrastructure Diagram" - "Network Topology" - "Security Architecture" stakeholders: ["CTO", "Infrastructure Team", "Security"]

capability_maturity: initial: "Ad-hoc, chaotic" repeatable: "Basic processes" defined: "Standardized" managed: "Measured" optimizing: "Continuous improvement"

anti_patterns:

• pattern: "Ivory Tower" problem: "Architecture disconnected from delivery" solution: "Embed architects in teams"
• pattern: "Analysis Paralysis" problem: "Endless planning, no delivery" solution: "Time-box phases, iterate"
• pattern: "Big Bang Transformation" problem: "All-or-nothing approach" solution: "Incremental transitions"
• pattern: "Technology-First" problem: "Choosing tech before understanding problem" solution: "Capability-driven design"
• pattern: "Documentation Overload" problem: "Diagrams no one reads" solution: "Just-enough, living documentation"
• pattern: "Governance as Gatekeeping" problem: "Architecture review as bottleneck" solution: "Enablement over control"

implementation_checklist: architecture_development: - "Business drivers and goals documented" - "Stakeholders identified and engaged" - "Current state assessed (AS-IS)" - "Target state defined (TO-BE)" - "Gap analysis completed" - "Roadmap with transition states" - "Governance model established" domain_driven_design: - "Core domains identified (invest heavily)" - "Supporting domains identified (buy or build)" - "Generic subdomains identified (buy/outsource)" - "Bounded contexts defined" - "Context map created" - "Ubiquitous language documented" governance: - "Architecture principles defined" - "Standards catalog maintained" - "Review process established" - "Exception process defined" - "Compliance monitoring in place" - "Architecture debt tracked"

handoffs:

• skill: integration-patterns trigger: "system integration architecture"
• skill: data-governance trigger: "data architecture governance"

ecosystem: frameworks: - "TOGAF" - "Zachman Framework" - "FEAF" modeling: - "ArchiMate" - "BPMN" - "UML" tools: - "Sparx Enterprise Architect" - "LeanIX" - "Ardoq"

sources: standards: - "TOGAF Standard" - "ArchiMate Specification" references: - "Domain-Driven Design Reference" - "Visual Paradigm TOGAF Guide"