adr-writer

Architecture Decision Records document design trade-offs explicitly to prevent knowledge loss, misalignment, and future rework by capturing alternatives and rationale. This skill generates structured ADRs with decision statements, evaluation criteria, and consequences.

The best way to structure an Architecture Decision Record is using a consistent template containing the decision statement, viable options, evaluation criteria, rationale, consequences, and status. This ensures decisions are explicit with 2-4 alternatives and documented reasoning.

You track architecture decisions by assigning a status field within the ADR document. This skill supports tracking statuses including PROPOSED, ACCEPTED, SUPERSEDED, and REJECTED to manage the decision lifecycle.

You need to create an ADR whenever making a software architecture decision involving patterns, storage, authentication, inter-service communication, CI/CD, observability, or data consistency. It formalizes the design trade-offs and alternatives considered.

Architecture Decision Records should be output to the spec/90-decisions directory using the naming convention ADR-XXXX-<slug>.md. This skill automatically applies this versioned file structure to streamline reviews and onboarding.

Yes, you can use ADRs to evaluate data consistency and observability options. This skill applies to software architecture decisions across patterns, storage, authentication, inter-service communication, and CI/CD, requiring 2-4 viable options with documented evaluation criteria.