adr-writer

Create Architecture Decision Records with context, alternatives, tradeoffs, and ownership.

5|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/patricio0312rev/skillset --skill adr-writer-patricio0312rev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr-writer
Source: https://github.com/patricio0312rev/skillset/tree/main/templates/architecture/adr-writer
Command: npx skills add https://github.com/patricio0312rev/skillset --skill adr-writer-patricio0312rev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions accumulate over time and are hard to trace, leading to inconsistent design and duplicated reasoning. This Skill helps teams capture decisions with context for future reference.

Core Features & Use Cases

  • Prose: Provides a standard ADR structure including Context, Decision, Alternatives, Consequences, Risks, and Owners.
  • Reuse: Templates and quick-start ensure ADRs are created consistently across projects.
  • Collaboration: Improves governance by making reasoning explicit during architecture reviews.

Quick Start

Create a new ADR using the ADR template and fill in sections such as Context, Decision, Alternatives, and Consequences to document a key architecture choice.

Frequently Asked Questions about adr-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document architecture decisions with context, alternatives, and tradeoffs?

To document architecture decisions, use an Architecture Decision Record (ADR) format with structured sections for Context, Decision, Alternatives, Consequences, Risks, and Follow-ups. This captures reasoning explicitly for future reference across teams.

How do I create an ADR template for consistent software design reviews?

Create an ADR template by defining standard sections for Context, Decision, Alternatives, Consequences, Risks, and Follow-ups. This ensures ADRs are created consistently across projects and makes reasoning explicit during architecture reviews.

Does documenting architecture decisions require specific dependencies or components?

Documenting architecture decisions with this ADR format requires no specific dependencies or components. It provides a standalone structured template and quick-start guide for immediate implementation in software projects.

Why should I use a structured ADR format instead of unstructured documentation for design decisions?

A structured ADR format prevents architecture decisions from becoming hard to trace over time. By standardizing sections for tradeoffs and ownership, it avoids inconsistent design and duplicated reasoning across teams during system evolution.

When do I need to document architecture decisions using an ADR?

You need an ADR when accumulating architecture decisions that become hard to trace, leading to inconsistent design. It is essential for software projects, design reviews, and tracking system evolution across teams.

Can I use an ADR template for team collaboration during architecture reviews?

Yes, you can use an ADR template to improve governance and team collaboration during architecture reviews. By making reasoning explicit with defined ownership, it ensures design decisions are traceable across teams.