spec-driven-development-architecturelisted

# Spec-Driven Development Architecture Translate the **Solution Architecture Document** into a concrete **per-feature implementation-ready design** — a Development Architecture Document describing the layer-placement map (each component → architectural layer + source-tree path), the design patterns prescribed for the feature, the module structure, the dependency wiring (DI graph), the per-component test-strategy hooks, and the `SEED-NNN` story seeds that `/create-story` consumes. Governed by **ADR-069**. This skill owns the **Development Architect** role: the micro / per-feature phase of the modernized DevForgeAI pipeline — the implementation-design layer that `backend-architect` previously improvised uncharted inside `/dev`, per story, under TDD time pressure, with no review gate (Gap E of ARCH-GAPS-001). ``` /create-solution-architecture (per epic) → /create-development-architecture (THIS SKILL, once per feature) → /create-story (story files with acceptance criteria) ``` **Input contract:** `solution-architecture-output.schema.json` v1.0 — the Solution Architecture Document, carried in a `<script type="application/json" id="solution-architecture-data">` data island inside its HTML file. **Output contract:** `development-architecture-output.schema.json` v1.0 — emitted as a self-contained HTML document with an embedded JSON data island (`<script type="application/json" id="development-architecture-data">`). **Scope boundary — design only.** This skill produces the Deve