Creates structured Markdown ADRs with metadata, alternatives, consequences, and filename patterns.
npx skills add https://github.com/tarunccet/pm-skills --skill adr-tarunccet
Please help me install this Agent Skill. Skill: adr Source: https://github.com/tarunccet/pm-skills/tree/main/pm-execution/skills/adr Command: npx skills add https://github.com/tarunccet/pm-skills --skill adr-tarunccet
Documenting the rationale behind significant technical and product choices is often skipped or lost, leaving future engineers and product managers unable to understand why systems evolved a certain way. This Skill ensures decisions are recorded with context, alternatives, trade-offs, and consequences so teams inherit reasoning alongside code.
Draft an ADR summarizing the decision to migrate the public API from REST to GraphQL, list at least three alternatives with pros and cons, state the recommended option and its primary trade-offs, and save the output as ADR-001-migrate-to-graphql.md.
High-intent search queries and answers about installing and using this skill.
To document architectural decisions, create structured architecture decision records (ADRs) that capture context, alternatives, and consequences. This Skill generates Markdown files with metadata, decision statements, and trade-offs so teams inherit reasoning alongside code.
The best way to format an architecture decision record is a Markdown template including metadata (date, status, deciders), a clear decision statement, alternatives with pros/cons and effort estimates, consequences, and a filename pattern like ADR-[NNN]-[decision-title].md.
You should create an architecture decision record during planning, design reviews, or technical spikes when making irreversible decisions, such as migrating an API from REST to GraphQL, selecting third-party vendors, or choosing system design patterns.
To manage changes to an accepted architecture decision record, create a new ADR that supersedes the previous one rather than modifying the original. This governance practice enforces immutability and maintains a historical trail of deprecated and superseded decisions.
Yes, you can use existing technical specs to generate an architecture decision record. The Skill validates context by prompting for missing inputs and incorporating provided PRDs, RFCs, or technical specifications before producing the final Markdown output.
Yes, this architecture decision record template supports vendor selection documentation. It captures alternatives with pros, cons, and effort estimates, making it suitable for recording third-party vendor choices and irreversible product decisions during design reviews.
kmshihab7878Guides users through structured, iterative co-authoring workflows for collaborative documents.
HeyItsGilbertCreate architecture decision records with frontmatter and body for documentation.
0xRayAIProvides tools for system design, architecture planning, and decision documentation.
hgflimaCreate and manage architectural decision records using markdown templates.
