architecture-decision-records

Document architecture decisions by capturing trade-offs into structured markdown files. This skill drafts records containing context, alternatives, and consequences during planning sessions to create a durable history.

The Nygard-style format structures decision records with context, decision, alternatives, and consequences sections. It produces lightweight markdown files with sequential numbering and index maintenance.

Create an ADR for framework and database choices by initiating a capture during planning sessions. The tool drafts a markdown file documenting the specific trade-offs and awaits your confirmation before writing.

Yes, you can read existing architecture decision records. It parses prior documents to explain why a specific choice was made and helps maintain the searchable index.

No, the tool respects confirmation gates before writing files. It drafts the architecture decision record for your review and only saves the markdown document after explicit approval.

You can capture API design, deployment, authentication, and testing strategy trade-offs in an ADR. The tool structures these software engineering decisions into markdown with alternatives and consequences.