What problem does it solve? Teams building a system in separate parts drift apart on the decisions that must stay consistent — boundaries, dependency direction, state mutation, shared data ownership. This Skill produces an architecture spine: a terse document that fixes only those invariants, so independently built units stay compatible. ## Core Features & Use Cases - Architecture spine authoring: Create, update, or validate an ARCHITECTURE-SPINE.md with stable AD-n decision blocks (Binds/Prevents/Rule), a named design paradigm, a pinned stack table, and a Deferred section, distilled from an append-only memlog. - Coaching or fast drafting: Work decisions out interactively through open-ended elicitation, or draft the whole spine fast with [ASSUMPTION] tags for review; brownfield runs ratify conventions found in the existing codebase. - Deterministic review gate: Run lint_spine.py to catch placeholders, duplicate AD IDs, missing fields, and unpinned versions, then dispatch parallel reviewer subagents against the spine. - Use Case: Point it at a spec package or an existing repository and ask for the architecture spine; it records each decision in a memlog, distills the spine, runs the reviewer gate, and hands off to spec or epic breakdown workflows. ## Quick Start Ask the assistant to create the architecture spine for your project from the current spec or codebase, choosing the coaching path when prompted.
