create-adr

Create Architecture Decision Records using Michael Nygard's template.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-adr-jerelvelarde
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-adr
Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/create-adr
Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-adr-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documents and justifies architectural decisions in a structured, traceable format so future engineers understand the reasoning, context, and trade-offs behind key choices.

Core Features & Use Cases

  • Template-driven ADR creation with context, decision, alternatives considered, and consequences.
  • Automated numbering and linking to related ADRs to preserve decision history.
  • Use cases include documenting major tech choices, evaluating options, and guiding team alignment during architecture shifts.

Quick Start

Provide a concise decision title and context for the ADR, and I will generate a complete ADR file with alternatives and consequences.

Frequently Asked Questions about create-adr

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

FAQPage Schema
What is an Architecture Decision Record and when should I create one?▼

An Architecture Decision Record (ADR) is a formal document that captures the context, alternatives, and consequences of a key technical choice. Create an ADR whenever your team makes a significant architectural shift that requires traceable justification.

How do I write an Architecture Decision Record using the Michael Nygard template?▼

To write an Architecture Decision Record using the Michael Nygard template, provide a concise decision title and context. The tool generates a complete file documenting the decision, alternatives considered, consequences, and a revisit trigger.

What's the best way to document architectural alternatives and consequences for engineering docs?▼

The best way to document architectural alternatives and consequences is using a structured ADR format. This ensures engineering docs capture the trade-offs and reasoning behind decisions, preserving decision history for future alignment.

Does this ADR generator include automated numbering and links to related decision records?▼

Yes, the ADR generator includes automated numbering and links to related decision records. This preserves decision history and ensures your architecture documentation remains traceable across multiple engineering docs.

Can I use a decision record template to guide team alignment during architecture shifts?▼

Yes, you can use a decision record template to guide team alignment during architecture shifts. By evaluating options and documenting consequences formally, the team gains a shared understanding of the technical trade-offs.

What must be included in a complete architecture decision record?▼

A complete architecture decision record must include the context, the decision itself, alternatives considered, consequences, and a concise revisit trigger. This ensures future engineers fully understand the architectural choice and its impact.