spec-driven-solution-architecturelisted

# Spec-Driven Solution Architecture Translate the **System Architecture Document** into a concrete **per-epic technical design** — a Solution Architecture Document describing the component decomposition, the interface contracts between those components, the solution data model, the integration design, and the epic's feature decomposition with feasibility verdicts. Governed by **ADR-068**. This skill owns the **Solution Architect** role: the meso / per-epic phase of the modernized DevForgeAI pipeline — the technical-design layer that was absent before (Gap A of ARCH-GAPS-001). ``` /create-system-architecture (constitution) → /create-solution-architecture (THIS SKILL, once per epic) → /create-development-architecture (per-feature implementation design) ``` **Input contract:** `system-architecture-output.schema.json` v1.0 — the System Architecture Document, carried in a `<script type="application/json" id="system-architecture-data">` data island inside its HTML file. **Output contract:** `solution-architecture-output.schema.json` v1.0 — emitted as a self-contained HTML document with an embedded JSON data island (`<script type="application/json" id="solution-architecture-data">`). **The constitution is THE LAW.** Components, layers, and contracts MUST respect `architecture-constraints.md` and `tech-stack.md`. If ambiguous or conflicting: HALT and use AskUserQuestion. --- ## Execution Model See **`.claude/rules/core/anti-skip-behavior.md`** for the canonical execution co