adr-authoring

An Architecture Decision Record (ADR) documents significant software architecture decisions, capturing context, options, and outcomes to ensure traceability. You need one when making structural choices that impact a project's design and require team alignment.

To write an ADR using MADR templates, describe your decision, context, and desired ADR level. The skill generates a structured document with sections like Context, Decision Drivers, Considered Options, Consequences, and Outcome.

Yes, this architecture decision record skill supports Lightweight, Standard, and Full ADR levels. It provides structured MADR-style templates tailored to each level to accelerate architecture decision documentation across various project scopes.

Yes, you can track the architecture decision lifecycle from proposal to acceptance or deprecation. The skill guides this process using MADR templates, ensuring full traceability and clear documentation of the decision's status over time.

MADR provides structured templates specifically designed for Architecture Decision Records, standardizing sections like Decision Drivers and Considered Options. Other category-level formats may lack this built-in lifecycle guidance from proposal to deprecation.

A generated architecture decision record includes sections for Context, Decision Drivers, Considered Options, Consequences, and Outcome. It also enforces a SKILL.md frontmatter with name and description, plus sections for the problem solved and quick start.