What problem does it solve? Teams lose the reasoning behind architectural choices over time, leaving future engineers guessing why a database, framework, or pattern was selected. This Skill captures the context, decision, and consequences of significant technical choices in durable, standardized ADR documents. ## Core Features & Use Cases - Three Industry Formats: Generates ADRs in MADR (structured options comparison), Nygard (minimal Context/Decision/Consequences), or Y-Statement (single-paragraph) formats. - Automatic Numbering and Naming: Scans your docs/adr/ directory to assign the next sequential number and enforces the NNN-kebab-case-title.md naming convention. - Multilingual Generation: Detects the user's language and writes the ADR in English, Portuguese, Spanish, or other languages automatically. - Use Case: After deciding to adopt GraphQL over REST, ask the agent to record the decision; it produces a numbered MADR document with considered options, decision drivers, honest trade-offs, and supersession links. ## Quick Start Ask the agent to write an ADR documenting your decision to use PostgreSQL as the primary database, including the alternatives you evaluated and why they were rejected.