What problem does it solve? Teams often lose track of why technical decisions were made, leaving future developers guessing about the reasoning behind architecture choices. This Skill captures decisions, alternatives, and trade-offs in a consistent MADR-format document. ## Core Features & Use Cases - MADR-Formatted ADRs: Generates a complete Architecture Decision Record with status, date, context, decision drivers, considered options, and consequences. - Sequential Numbering: Saves the ADR to docs/decisions/NNNN-title.md, automatically determining the next sequential number. - Interactive Review: Walks through the draft with the user to verify options are represented fairly and trade-offs are captured. - Use Case: After choosing PostgreSQL over MongoDB for a new service, ask the Skill to document the decision — it produces a structured ADR recording the drivers, rejected alternatives, and consequences. ## Quick Start Ask the assistant to write an ADR documenting why you chose a specific technology or approach, providing the context and options considered.