What problem does it solve? When a project intentionally diverges from an architecture guideline rule, the decision is often lost in review threads or left undocumented, causing repeated findings in future reviews. This Skill records the deviation as a formal Architecture Decision Record so reviews treat the cited code as a documented exception rather than a finding. ## Core Features & Use Cases - ADR Generation: Resolves the deviated rule from the lens catalog and guideline, quotes the principle verbatim, and writes a numbered ADR (NNNN-<slug>.md) under docs/adr/ with context, decision, and consequences. - Checker Integration: Produces the matching arch-check configuration entry (disable, exception, or inline ignore comment) so the static checker passes on code covered by the ADR. - Deviations Table Maintenance: Appends a summary row to the specs/architecture.md deviations table when one exists. - Use Case: A reviewer flags that a service bypasses the storage layer (lens STO-02), and the team decides the bypass is intentional for a read-only reporting path. Run the Skill with the lens id and reason to produce ADR-0007, the pyproject.toml exception entry, and the inline comment to cite beside the code. ## Quick Start Ask the AI to record a deviation from lens STO-02 with the reason that the reporting service reads replicas directly, and have it write the ADR and arch-check entry.
