decision-records

Writes and audits concise architecture decision records (MADR or Y-statement) with alternatives, consequences, revisit triggers and a staleness rubric. Use when a technical decision is made, changed, questioned or needs writing up for future developers, when existing records need an audit, or to find the recorded rationale of an existing decision (check docs/adr first); a casual "why" question about a piece of code does not need it.