Architecture Decision Records

Canonical owner for ADR creation in a project: detect or accept invocation, draft, get approval, write the ADR, initialize scaffolding if needed, and update the index.

Default shape: minimal structure, rich rationale — title plus prose that covers context, decision, why, and trade-offs. Optional expanded sections when the decision needs more room.

When to activate

• User says "ADR this", "record this decision", or invokes /architecture-decision-records
• User chooses between significant alternatives (framework, datastore, API shape, auth)
• User says "we decided to…" or "the reason we're doing X instead of Y is…"
• User asks "why did we choose X?" (read existing ADRs)
• Architectural trade-offs during planning (offer only — see below)

User clarifications (Cursor)

For discrete decisions (about 2–6 options), prefer AskQuestion, one decision at a time. If unavailable, ask the same options in chat. Use plain chat for free-form rationale.

Offer vs write