What problem does it solve? Engineering teams lose the reasoning behind significant technical choices, causing future developers to relitigate settled decisions or accidentally reverse them. This Skill captures each architecture decision—context, options, choice, and consequences—as a durable, numbered record in the repo. ## Core Features & Use Cases - Append-only ADR log: Creates docs/adr/NNNN-<slug>.md files with a MADR-flavored template (context, decision drivers, options, decision, consequences) plus a README index table. - Convention detection: Adopts an existing ADR directory's numbering, headings, and status vocabulary instead of imposing a new format. - Decision discipline: Applies a three-question litmus test (expensive to undo, cross-cutting, surprising) to decide whether a choice warrants a record, and enforces honest trade-offs for every option. - Use Case: After choosing Postgres over DynamoDB for workflow state, record the decision as ADR-0003 with the rejected options' rationale, so future engineers understand why without reopening the debate. ## Quick Start Use the adr skill to record our decision to adopt event sourcing for the billing service as a new ADR in this repo.
