What problem does it solve?
This Skill helps teams capture important architecture and design decisions in a durable ADR instead of leaving the reasoning buried in chats, meetings, or memory. It reduces the risk of future confusion about why one option was chosen over another and keeps decision records consistent with the repository's existing conventions.
Core Features & Use Cases
- Convention Discovery: Finds the repository's ADR folder, naming pattern, numbering scheme, and document style before drafting anything.
- Interactive Decision Framing: Pulls out the real forcing function, alternatives considered, and consequences so the ADR reflects an actual decision instead of vague documentation.
- Repo-Matched Drafting: Writes a concise ADR that fits local formatting, status conventions, and linking practices, including superseding older ADRs when needed.
- Use Case: Ideal when a team has decided on a database change, library adoption, deployment topology, or other architectural direction and wants a clear written record in the codebase.
Quick Start
Ask the assistant to use write-adr to document a specific architecture decision and include the decision, the alternatives considered, and why the change is happening now.