What problem does it solve? Architectural decisions and coding norms often live in scattered conversations or get lost entirely, making it impossible to know why a technology was chosen or what rules the project must follow today. This Skill maintains two distinct, cross-linked documents: immutable ADRs recording the "why" of each decision, and living domain standards (testing, API, security, etc.) recording the "what must be complied with now" as RFC 2119 requirements with verifiable compliance criteria. ## Core Features & Use Cases - ADR lifecycle management: Create, update, deprecate, or supersede Architecture Decision Records in docs/adr/ with conflict validation against existing accepted decisions. - Domain standards with compliance criteria: Maintain normative standards in docs/standards/ where each requirement carries measurable CR-XXX criteria, proposed to the user in a selection table before anything is written. - Fitness functions and runner: Register automated architecture checks per standard in scripts/arch/checks/ written in the repo's own stack language, orchestrated by a single verify runner usable as a CI quality gate. - Use Case: After deciding "unit tests must use Vitest with coverage ≥ 80%", invoke the Skill to record ADR-003, add the requirement to Testing Standards, and generate a blocking fitness function that fails CI when coverage drops below the threshold. ## Quick Start Ask the agent to register an architectural decision, for example: document why we adopted GraphQL for the API and add the corresponding requirement to the API standards.
