adr-writer

To document architectural decisions in MADR format, this skill generates complete Architecture Decision Records with mandatory sections including frontmatter, context, options, decision, and consequences. It validates the records against MADR 4.0.0 phrasing rules and commits them directly to your docs/decisions/ directory.

Superseding an existing architecture decision record involves creating a new ADR that references and replaces the old one. This skill manages the supersede flow by generating the new record, updating the decision index, and committing the changes to maintain traceability.

Yes, the ADR writer validates mandatory sections and phrasing rules. It checks that your architecture decision records strictly adhere to the MADR 4.0.0 format, ensuring all required components like frontmatter, context, options, decision, and consequences are present and correctly structured.

You can integrate web research for supporting evidence when writing an ADR. This skill incorporates web research capabilities to gather supporting evidence for your architectural decisions and logs session IDs to ensure full traceability of the gathered context.

Architecture decision records are committed to the docs/decisions/ directory. After writing and validating the ADR in MADR 4.0.0 format, the skill automatically updates the decision index to reflect the new or superseded records.

You should use a standardized decision record instead of informal technical documentation when a team makes a significant architectural choice, such as adopting a new database technology. It formally documents the decision, the options considered, and the rationale behind the choice for future reference.