adr-generator

Document architecture decisions using the Michael Nygard ADR format.

28|3|Updated Mar 7, 2026

Search Tags:#architecture #documentation #adr #governance #design-decision #decision-record

Ready to run

npx skills add https://github.com/girijashankarj/cursor-handbook --skill adr-generator-girijashankarj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adr-generator
Source: https://github.com/girijashankarj/cursor-handbook/tree/main/.cursor/skills/documentation/adr-generator
Command: npx skills add https://github.com/girijashankarj/cursor-handbook --skill adr-generator-girijashankarj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions are often undocumented, leading to repeated debates, misaligned implementations, and loss of rationale over time. The ADR Generator standardizes recording these decisions using the Michael Nygard format to preserve context, options, and consequences for future teams.

Core Features & Use Cases

Create ADRs following the Michael Nygard format to capture context, options, decisions, and consequences.
Auto-increment ADR numbers and store them under docs/adr for centralized traceability.
Use ADRs during design reviews, migrations, and major architectural trade-offs to improve decision quality and onboarding.

Quick Start

Outline the problem, options, and decision, then save the ADR under docs/adr with sequential numbering.

Frequently Asked Questions about adr-generator

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

FAQPage Schema

How do I document architectural decisions to prevent knowledge loss across teams?▼

Documenting architectural decisions requires capturing context, options, decisions, and consequences in a formal record. Using the Michael Nygard ADR format standardizes this process, preserving rationale for future teams and preventing repeated debates during system migrations.

What is the standard structure for an Architecture Decision Record?▼

An Architecture Decision Record requires a minimal structure comprising Context, Decision, Options, and Consequences. This format ensures all technical trade-offs and design decisions are recorded systematically to improve onboarding and decision quality.

How do I auto-increment and store ADR files for centralized traceability?▼

To store ADRs with centralized traceability, save each record under the docs/adr directory using sequential numbering. Auto-incrementing ADR numbers ensures chronological ordering and easy referencing during design reviews.

When do I need to create an Architecture Decision Record?▼

You need an Architecture Decision Record during design reviews, system migrations, and major technical trade-offs. Creating ADRs in these scenarios ensures that architectural rationale is formally documented and aligned across multiple teams.

What is the best way to standardize technical trade-off documentation across teams?▼

The best way to standardize technical trade-off documentation is applying a formal ADR process. Capturing context, options, and consequences using the Michael Nygard format aligns implementations and prevents misaligned architectural decisions.

Can I use ADRs for onboarding new engineers to existing system architectures?▼

Yes, ADRs are highly effective for onboarding engineers. By documenting context and consequences under docs/adr, new team members can trace the rationale behind past design decisions and system migrations quickly.