| name | develop-adr |
| description | 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. |
| license | Apache-2.0 |
| metadata | {"phase":"develop","version":"2.1.0","updated":"2026-06-10T00:00:00.000Z","category":"specification","frameworks":["triple-diamond","lean-startup","design-thinking"],"author":"product-on-purpose"} |
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:
-
Assign a Number and Title
ADRs are numbered sequentially (ADR-001, ADR-002, etc.) for easy reference. The title should be a short noun phrase describing the decision, like "Use PostgreSQL for order data" or "Adopt React for frontend."
-
Set the Status and Decision Provenance
New ADRs start as "Proposed." After team review, they become "Accepted," "Deprecated," or "Superseded by ADR-XXX." Status changes should be tracked. Because this pipeline is agent-driven across multiple hosts and models, also record the decision's provenance in the Status section: the agent (e.g. claude-code, codex, cursor), the model (e.g. claude-opus-4-8), and the trigger (user-prompt, autonomous, or review-driven). This keeps a P7 architecture decision auditable later, regardless of which agent or model produced it.
-
Describe the Context
Explain the circumstances that led to this decision. What problem are you solving? What forces are at play (technical constraints, team expertise, timeline, cost)? This section should help a reader who wasn't there understand why this decision was needed.
-
State the Decision
Clearly articulate what you decided. Use active voice: "We will use..." rather than "It was decided..." Be specific about what is and isn't included in the decision.
-
Document the Consequences
List the outcomes of this decision - positive, negative, and neutral. Good ADRs are honest about trade-offs. What becomes easier? What becomes harder? What new constraints or options does this create?
Output Format
Use the template in references/TEMPLATE.md to structure the output. A complete ADR fills every template section: Status (including decision provenance — agent, model, trigger); Context; Decision; Consequences; Alternatives Considered; and References.
Quality Checklist
Before finalizing, verify:
Examples
See references/EXAMPLE.md for a completed example.
