governance-author-adr

You document architectural decisions by creating repository-aware Architecture Decision Records that capture technical rationale and preserve tradeoffs. This ensures future contributors understand decisions without revisiting past discussions.

An ADR is an Architecture Decision Record used to capture load-bearing architectural choices. You need to create one when your team chooses a new persistence approach or defines an architectural boundary to preserve the technical reasoning.

Drafting a MADR-style decision record involves identifying the architectural decision, validating architectural facts, and applying structured documentation practices following repository conventions to enforce consistent decision governance.

Yes, the decision governance workflow explicitly supports supersession scenarios. It guides the suggestion, authoring, and supersession processes while enforcing validation and review rules to maintain decision history.

The best way to govern ADR reviews is to apply a structured documentation workflow that enforces validation, review, and documentation rules. This ensures architectural facts are verified and decision records remain consistent.

You should avoid creating ADRs for non-load-bearing decisions. This Skill specifically targets architectural decisions where preserving technical rationale prevents repeated debate over significant tradeoffs and architectural boundaries.