What problem does it solve? Proposed Architecture Decision Records often contain placeholder residue, broken cross-references, or claims that do not match the actual codebase, and teams lack a consistent way to verify a record is ready before ratification. ## Core Features & Use Cases - Structural Validation: Checks required sections (Context, Decision, Consequences), placeholder residue, header sanity, and cross-reference integrity via the adr MCP audit action. - Codebase Grounding: Verifies that files, modules, versions, and configuration values cited in the record actually exist and match the repository. - Formal Auto-Fixes with Verdict: Mechanically fixes formatting, links, and fillable placeholders, then issues a READY_FOR_ACCEPTANCE verdict or a numbered defect list. - Use Case: After drafting ADR-0031 with /marvin:adr, run this review to confirm every claim is grounded in the repo and formal defects are fixed before a human ratifies it with /marvin:adr-accept. ## Quick Start Ask the assistant to review ADR 31 and tell you whether it is ready for acceptance.