What problem does it solve? Architectural decisions often go undocumented or are recorded inconsistently, making it impossible for teams to understand why choices were made. This Skill standardizes the creation, validation, and lifecycle management of Architecture Decision Records (ADRs) so every decision is captured in a consistent, machine-readable format. ## Core Features & Use Cases - Structured ADR Authoring: Combines OKF-compliant YAML frontmatter (type, title, deciders, status, generated provenance) with a MADR 4.0 body covering context, options, and outcomes. - Lifecycle Management: Handles the full status lifecycle (proposed, rejected, accepted, deprecated, superseded) including bidirectional supersede links and per-directory numbering that is never reused. - Automated Validation: Ships a Python validator that checks frontmatter fields, required MADR sections, filename conventions, and title/H1 consistency for single files or entire directories. - Use Case: After merging a pull request that switches the database from MySQL to PostgreSQL, ask the agent to document the decision; it discovers the existing ADR directory, assigns the next sequence number, drafts the ADR from git diffs, and validates it. ## Quick Start Ask the agent to create an ADR documenting why the project adopted PostgreSQL, and have it validated with the included script.