What problem does it solve? Architecture Decision Records often become zombie documents that nobody enforces. This Skill writes ADRs whose mechanical constraints carry an executable enforced_by grep/lint rule, so a verifier can automatically fail builds that violate the decision instead of relying on human memory. ## Core Features & Use Cases - Mechanical vs discursive ADRs: Distinguishes constraints verifiable by grep/lint rules (checked by the mismagent-verifier) from judgment-based ones (checked by code review). - Portable, false-green-proof rules: Enforces POSIX-portable, shell-safe grep rules anchored to code constructs (imports, declarations) rather than filenames or bare tokens, with comment-stripping and positive/negative fixture validation. - Lifecycle management: Handles progressive numbering, superseding old ADRs, closing open spikes via closes_spike, wave-gated presence rules, and reconciliation with the context-map and profile boundary rules. - Use Case: During the model movement of a feature, record the decision "no wall-clock calls in domain code" as an ADR whose enforced_by grep covers System.currentTimeMillis, Instant.now(), and Clock.systemUTC(), so the verifier fails any violating diff. ## Quick Start Ask the agent to write an ADR for a specific architectural decision, for example: write an ADR forbidding direct database access from the frontend module with an enforced grep rule.
