adr-format-nygard

Explain the Nygard ADR format template with five-section structure in Markdown.

5|3|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/zircote/adr --skill adr-format-nygard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr-format-nygard
Source: https://github.com/zircote/adr/tree/main/skills/adr-format-nygard
Command: npx skills add https://github.com/zircote/adr --skill adr-format-nygard

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Nygard ADRs provide a simple, time-tested format to capture decisions, context, and consequences in a lightweight template that reduces ambiguity and saves time during architecture discussions.

## Core Features & Use Cases

  • Simple, five-section structure for quick decision documentation.
  • Neutral context, clear decisions, and explicit consequences for future reference.
  • Use Case: documenting ADRs for a new API design or a major refactor to ensure consensus.

### Quick Start Create a new ADR document following the Nygard template and populate the Context, Decision, and Consequences sections accordingly.

Frequently Asked Questions about adr-format-nygard

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

FAQPage Schema
What is the Nygard ADR format for architecture decision records?

The Nygard ADR format is a lightweight, five-section Markdown template for documenting architecture decisions, context, and consequences to reduce ambiguity during project discussions.

How do I write an architecture decision record using the five-section structure?

To write an architecture decision record, populate the five Markdown sections with neutral context, a clear decision statement, and explicit consequences to ensure future reference and team consensus.

When should I use a lightweight ADR template for documenting software decisions?

Use a lightweight ADR template for quick documentation tasks like capturing a new API design or a major refactor, ensuring simple historical records remain consistent across projects.

What is the best way to document architecture decisions for a new API design?

The best way to document architecture decisions is applying the Nygard template to capture neutral context, clear decisions, and explicit consequences for future reference and team consensus.

Do I need prior knowledge of the Nygard structure to document decision records?

You need knowledge of the five-section structure and guidance on writing neutral context with clear Markdown section labeling to effectively document decision records using this format.

Why does my architecture documentation lack consensus during major refactors?

Architecture documentation lacks consensus when missing explicit consequences and neutral context. Applying the Nygard decision record format captures these elements to ensure team alignment.