
Develop Adr
This creates Architecture Decision Records in Michael Nygard's format, documenting why you made technical choices so future developers understand the reasoning behind architectural decisions. Use it when picking frameworks, databases, or establishing development patterns that'll affect the codebase long term. It walks you through numbering, status, context, the actual decision, and consequences (both good and bad). The honest trade-offs section is the real value here. Too many teams skip documenting architecture decisions and then wonder six months later why they chose PostgreSQL over MongoDB. It includes a template and quality checklist to keep ADRs consistent across your project.
- skills.sh installs
- 842
- GitHub stars
- 794
- last updated
- Aug 21, 2026
Install
$ npx -y skills add product-on-purpose/pm-skills --skill develop-adr --agent claude-codeInstalls into .claude/skills of the current project.
Files
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
Sponsors
Details
- Repository
- github.com/product-on-purpose/pm-skills
- Categories
- Code Review & Quality, Productivity & Planning
- First seen
- Jun 3, 2026
More from product-on-purpose/pm-skills
All 68- Deliver Launch Checklist834
- Develop Solution Brief830
- Define Opportunity Tree824
- Discover Interview Synthesis819
- Define Jtbd Canvas817
- Measure Dashboard Requirements801
- Measure Experiment Design801
- Deliver Release Notes797
- Develop Design Rationale793
- Foundation Persona792
- Measure Instrumentation Spec792
- Measure Experiment Results787
- Iterate Retrospective786
- Utility Mermaid Diagrams786
- Discover Stakeholder Summary779
- Foundation Okr Writer776
- Develop Spike Summary774
- Iterate Lessons Log767
- Iterate Pivot Decision767
- Utility Slideshow Creator764
- Foundation Lean Canvas762
- Iterate Refinement Notes753
- Utility Pm Skill Builder751
- Foundation Meeting Agenda749