develop-adr

Generate Architecture Decision Records using the Nygard-style ADR template.

527|69|Updated Jan 9, 2026

Search Tags:#architecture #documentation #adr #design-patterns #decision-record #nygard

Ready to run

npx skills add https://github.com/product-on-purpose/pm-skills --skill develop-adr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: develop-adr
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-adr
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill develop-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams generate Architecture Decision Records to document significant technical decisions.

Core Features & Use Cases

Lightweight ADR format that records decision number, title, context, decision, and consequences.
Sequential numbering (ADR-001, ADR-002, etc.) for easy reference.
Guided templates and a quick-start workflow to create, review, and maintain architectural decisions across projects.

Quick Start

Create an ADR-001: [Title] and populate Context, Decision, and Consequences sections using the template in references/TEMPLATE.md, then store the document alongside the project ADRs.

Frequently Asked Questions about develop-adr

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

FAQPage Schema

What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) documents significant technical choices affecting system architecture, technology selection, or development patterns. You need an ADR when a decision impacts your project across time and requires clear context, decision, and consequences tracking.

How do I write an ADR using the Nygard format?▼

To write an ADR using the Nygard format, populate a template with sequential numbering, a title, context, decision, and consequences sections. Store the generated document alongside your project's existing ADRs for easy reference.

What should be included in the context and consequences sections of an ADR?▼

The context section of an ADR should describe the technical problem and constraints driving the decision, while the consequences section details the impacts, trade-offs, and effects on the system architecture after the decision is made.

How do I number and organize Architecture Decision Records across projects?▼

Architecture Decision Records are organized using sequential numbering like ADR-001 and ADR-002. Apply this lightweight numbering format consistently and store the documents alongside your project codebase to maintain a clear history of technical decisions.

Can I use ADRs for documenting technology selection and development patterns?▼

Yes, Architecture Decision Records are explicitly designed for documenting technology selection and development patterns. The lightweight format captures the context and consequences of these decisions, ensuring significant architectural choices are tracked across projects.