draft-adr

Research a problem space and draft an Architecture Decision Record (ADR).

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jamesc/skills --skill draft-adr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: draft-adr
Source: https://github.com/jamesc/skills/tree/main/skills/draft-adr
Command: npx skills add https://github.com/jamesc/skills --skill draft-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of researching a problem, exploring trade-offs, and drafting a comprehensive Architecture Decision Record (ADR) to document significant technical decisions.

Core Features & Use Cases

  • Structured Decision Making: Guides users through a rigorous process of defining, researching, and evaluating architectural choices.
  • Comprehensive Documentation: Ensures ADRs capture the 'why' behind decisions, including context, options, trade-offs, and impact on various stakeholders.
  • Use Case: When a significant architectural change is proposed, like adopting a new database technology or altering a core communication protocol, this skill helps create a well-reasoned ADR that serves as a historical record and future reference.

Quick Start

Use the draft-adr skill to research and draft an ADR for the problem of implementing a new caching layer.

Frequently Asked Questions about draft-adr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft an Architecture Decision Record for a new software design?▼

To draft an Architecture Decision Record, you research the problem space, analyze trade-offs across user personas, and document the context, options, and impact to establish a historical technical record.

When do I need to create an ADR for technical documentation?▼

You need to create an ADR when proposing a significant architectural change, such as adopting a new database technology or altering a core communication protocol, to capture the reasoning behind the decision.

What is the best way to document architectural trade-offs and stakeholder impact?▼

The best way to document architectural trade-offs is by following established ADR conventions that capture the context, compare prior art, and evaluate the impact on various stakeholders for future reference.

How do I research prior art and analyze code for an architecture decision record?▼

You research prior art and analyze code by reviewing existing documentation, comparing solutions against multiple user personas, and evaluating technical trade-offs to inform the architecture decision-making process.

Can I use a structured process to evaluate architectural choices before adopting them?▼

Yes, you can use a structured decision-making process to rigorously define, research, and evaluate architectural choices before drafting a comprehensive technical decision record for your software engineering project.

What limitations exist when automating architecture decision documentation?▼

Automating architecture decision documentation relies on available code analysis and documentation review, so limitations arise when prior art is undocumented or when problem spaces lack clear user personas to analyze.