What problem does it solve? Software projects drift when independently built components make incompatible choices about boundaries, state mutation, data ownership, and stack versions. This Skill produces an architecture spine — a lean consistency contract that fixes only the non-obvious invariants, keeping everything built from it coherent without bloated documentation. ## Core Features & Use Cases - Architecture Spine Generation: Distills decisions into stable AD-n blocks (Binds/Prevents/Rule), a named design paradigm, consistency conventions, a pinned stack table, and mermaid structural diagrams, with an append-only memlog as working memory. - Coaching or Fast Path: Elicits decisions from the user through open-ended coaching by default, or drafts the full spine with [ASSUMPTION] tags for fast review. - Brownfield & Inherited Spines: Ratifies conventions from an existing codebase, or inherits a parent spine's ADs as read-only constraints when working at epic altitude. - Reviewer Gate: Runs a deterministic lint_spine.py pass plus parallel reviewer subagents against a good-spine checklist before handoff, with a standalone Validate intent producing an HTML report. - Use Case: Given a SPEC.md for a new feature, produce ARCHITECTURE-SPINE.md that fixes the paradigm, boundary rules, and pinned stack so multiple developers or agents build compatible modules. ## Quick Start Ask the assistant to create the architecture for your project or spec, and choose the Coaching path when prompted.
