enterprise-solution-architecturelisted

# Enterprise Solution Architecture Skill ## Intent Enterprise systems must remain coherent as multiple REQs are generated, evaluated, promoted, and finalized. This skill prevents fragmented slices, inconsistent contracts, duplicated composition roots, cloud-only assumptions, weak auditability, missing run paths, and business logic spread across unrelated modules. ## Use when Use this skill when the solution involves: - enterprise users or departments; - backoffice or operator workflows; - RBAC or identity; - auditability; - persistence; - document/workflow platforms; - integrations; - multi-service runtime; - on-prem/hybrid/cloud profiles; - regulated data; - AI features in an enterprise context. ## Do not use when Do not use this skill for isolated scripts, throwaway demos, simple static sites, or non-enterprise prototypes without integration/runtime obligations. ## Required architecture behavior Generated REQs and KITs must: - preserve stable public contracts; - respect existing module boundaries; - avoid duplicate domain models; - keep business APIs profile-independent; - keep runtime-specific logic behind adapters; - preserve audit semantics where actions are business-relevant; - use explicit configuration for runtime/environment behavior; - keep a local deterministic execution path; - avoid broad speculative architecture; - document production vs local-dev gaps honestly. ## Composition expectations When multiple slices are promoted, FINALIZE or an integratio