ADR Review

Review ADRs as architectural records that must remain useful to future maintainers. An ADR review is an audit and recommendation pass, not a rewrite pass unless the user explicitly asks for edits.

Ground Rules

• Read docs/adr/INDEX.md first.
• Audit the full ADR set: list docs/adr/ so every file is accounted for — the directory listing, not the index alone, is the inventory.
• Read individual ADR files according to the full-audit plan; read related ADRs together when they form a decision chain.
• Report findings and concrete proposed edits; apply edits only when the user asks.
• Use current code and docs as evidence. A newer preference alone does not make an ADR stale — report the contradiction, missing supersession, or drift it reveals.
• Run the review at the points drift is born, not only on request: the end of a superpowers plan run or after a large merge, where a decision may have been made in the flow and never written down.
• If editing is requested, also follow the adr skill's update/supersede workflow.

Full ADR Audit