develop-adr

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Architecture Decision Record (ADR)
3 
4An 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.
5 
6## When to Use
7 
8- Making significant technical decisions that affect system architecture
9- Choosing between technology options (frameworks, databases, services)
10- Establishing patterns that future development should follow
11- Documenting the rationale for constraints or non-obvious approaches
12- Preserving institutional knowledge about past decisions
13 
14## When NOT to Use
15 
16- The decision is a product or UX design choice, not architecture or technology -> use `develop-design-rationale`
17- You are still exploring whether an approach is feasible -> time-box the exploration and record it with `develop-spike-summary` first
18- You need to pitch a solution to stakeholders -> use `develop-solution-brief`; an ADR records a decision, it does not sell one
19- Nothing is actually being decided (the status quo continues unchanged): an ADR without a decision is noise; wait until there is one
20 
21## Instructions
22 
23When asked to create an ADR, follow these steps:
24 
251. **Assign a Number and Title**
26…