What problem does it solve? Teams building a system in separate parts drift apart on the decisions that must stay consistent — boundaries, state mutation, shared data ownership. This Skill captures those invariants in a terse architecture spine document so independently built units stay compatible. ## Core Features & Use Cases - Architecture spine authoring: Distills decisions into stable AD-n blocks (Binds/Prevents/Rule) with a named paradigm, stack pins, and mermaid diagrams, working from a spec, a raw idea, or an existing codebase. - Coaching or fast drafting: Elicits decisions through open-ended questioning by default, or drafts the full spine with [ASSUMPTION] tags for review when speed matters. - Deterministic review gate: Runs lint_spine.py for mechanical checks (placeholders, duplicate AD IDs, unpinned versions) plus parallel reviewer subagents before handoff. - Use Case: Point it at a brownfield repository 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 produces ARCHITECTURE-SPINE.md. ## Quick Start Ask the assistant to create the architecture spine for your project from the current spec or codebase.