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.
npx -y skills add product-on-purpose/pm-skills --skill develop-adr --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
juliusbrussee/caveman
mattpocock/skills
shadcn/improve
obra/superpowers
forrestchang/andrej-karpathy-skills
vercel-labs/skills