What problem does it solve? Teams building separate parts of a system drift into incompatible choices. This Skill produces an architecture spine — a short document fixing only the invariants (paradigm, boundaries, state mutation, data ownership) that keep independently built units consistent. ## Core Features & Use Cases - Create, update, or validate a spine: Works from a spec, a raw idea, or an existing codebase, at initiative, feature, or epic altitude, with stable AD-n decision IDs. - Coaching or Fast path: Elicits decisions through open-ended questions by default, or drafts the full spine with [ASSUMPTION] tags for review. - Reviewer Gate: Runs a deterministic lint_spine.py pass plus parallel reviewer subagents against a good-spine checklist before handoff. - Use Case: Point it at a brownfield codebase to ratify existing conventions into an ARCHITECTURE-SPINE.md with a memlog of every decision, then validate it before handing off to story-level work. ## Quick Start Ask the assistant to create the technical architecture for your project from your spec or existing codebase.