Develop Adr

Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.

819 stars 104 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add product-on-purpose/pm-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add product-on-purpose/pm-skills --skill develop-adr
Manual install
git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/skills/develop-adr ~/.claude/skills/develop-adr

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Architecture Decision Record (ADR)

An Architecture Decision Record documents a significant technical decision along with its context and consequences. ADRs capture the "why" behind architectural choices so future team members understand the reasoning - especially important when they question why something was done a particular way. This skill follows Michael Nygard's lightweight ADR format.

## When to Use

- Making significant technical decisions that affect system architecture
- Choosing between technology options (frameworks, databases, services)
- Establishing patterns that future development should follow
- Documenting the rationale for constraints or non-obvious approaches
- Preserving institutional knowledge about past decisions

## When NOT to Use

- The decision is a product or UX design choice, not architecture or technology -> use `develop-design-rationale`
- You are still exploring whether an approach is feasible -> time-box the exploration and record it with `develop-spike-summary` first
- You need to pitch a solution to stakeholders -> use `develop-solution-brief`; an ADR records a decision, it does not sell one
- Nothing is actually being decided (the status quo continues unchanged): an ADR without a decision is noise; wait until there is one

## Instructions

When asked to create an ADR, follow these steps:

1. **Assign a Number and Title**
Read the full skill on GitHub

Details

Skill name
develop-adr
Path
skills/develop-adr/SKILL.md
License
Apache-2.0
Repo updated
17 November 2026

FAQ

What does the Develop Adr skill do?

Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.

How do I install the Develop Adr skill?

Claude Code plugin: /plugin marketplace add product-on-purpose/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Develop Adr popular?

It lives in product-on-purpose/pm-skills, which has 819 GitHub stars and 104 forks, and is included in 2 curated skill lists.

Related skills

<phase or Classification Skill Name>

819

product-on-purpose/pm-skills

<single-line 20-100 word description; include trigger keywords and do not use folded YAML>

Skill & Plugin AuthoringIn 2 lists104

Define Hypothesis

819

product-on-purpose/pm-skills

Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.

Finance & CryptoIn 2 lists104

Define Jtbd Canvas

819

product-on-purpose/pm-skills

Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.

Frontend & DesignIn 2 lists104

Develop Design Rationale

819

product-on-purpose/pm-skills

Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied. Use when making significant UX decisions, aligning with stakeholders on design direction, or preserving design context for future reference.

Software DevelopmentIn 2 lists104

Define Prioritization Framework

819

product-on-purpose/pm-skills

Run applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives. Produces a comparison table showing where rankings agree and diverge across frameworks, and an executive summary with recommendation. Framework applicability is filtered by data availability; Kano requires customer research. Refuses to fabricate scores; produces an estimation scaffold when input data is missing.

Software DevelopmentIn 2 lists104

Develop Solution Brief

819

product-on-purpose/pm-skills

Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs. Use when pitching solutions to stakeholders, aligning teams on approach, or documenting solution intent before detailed specification.

Software DevelopmentIn 2 lists104

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.