What problem does it solve? Teams building a system in separate parts drift apart on boundaries, state mutation, and shared data ownership. This Skill produces a terse architecture spine that fixes only the invariants keeping independently built units consistent, so downstream builders cannot diverge. ## Core Features & Use Cases - Architecture spine authoring: Create a decision-focused ARCHITECTURE-SPINE.md with stable AD-n entries (Binds/Prevents/Rule), a named design paradigm, a pinned stack table, and mermaid structural diagrams, working from a spec, a raw idea, or an existing codebase. - Coaching or fast drafting: Elicit decisions through open-ended coaching questions, or draft the full spine quickly with [ASSUMPTION] tags for review. - Deterministic review gate: Lint the spine for placeholders, duplicate AD IDs, missing fields, and unpinned versions, then run parallel reviewer subagents before handoff. - Use Case: Point it at a brownfield codebase and ask it to derive an architecture spine; it ratifies the conventions the code already shows, logs every decision to an append-only memlog, and distills a validated spine document. ## Quick Start Ask the assistant to create the technical architecture for your project from your spec or existing codebase, choosing the coaching path to work through the decisions together.
