skills.rest
zircote
zircoteCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

adr-decision-drivers

Identify and document decision drivers for architectural ADRs.

5|3|Updated Jan 17, 2026
Search Tags:#architecture#documentation#adr#decision#trade-offs#drivers#quality-attributes
One-click install
npx skills add https://github.com/zircote/adr --skill adr-decision-drivers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr-decision-drivers
Source: https://github.com/zircote/adr/tree/main/skills/adr-decision-drivers
Command: npx skills add https://github.com/zircote/adr --skill adr-decision-drivers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Identifying and documenting the forces, concerns, and requirements that influence architectural decisions in ADRs, ensuring decisions are well-justified.

Core Features & Use Cases

  • Categorizes decision drivers across functional, quality attributes, constraints, business, technical, and team perspectives.
  • Provides discovery questions to surface drivers and a structured approach to documenting trade-offs.
  • Includes guidance on quality attributes, documentation templates, and several ADR-focused patterns for evaluation.
  • Useful in ADR creation, review, and governance to align stakeholders and justify choices.

Quick Start

Ask me to outline the decision drivers for a new ADR and capture them in the ADR decision drivers guide.

Frequently Asked Questions about adr-decision-drivers

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

FAQPage Schema
What are ADR decision drivers in software architecture?▼

ADR decision drivers are the forces, concerns, and requirements that influence architectural decisions. They span functional, quality attribute, business, technical, and team perspectives to ensure architectural choices are well-justified.

How do I document trade-offs in an architectural decision record?▼

Document trade-offs in an ADR by categorizing decision drivers across functional, quality, business, and technical concerns. Use structured discovery questions to surface and prioritize these competing quality attributes.

What's the best way to identify quality attributes for architecture decisions?▼

The best way to identify quality attributes is applying discovery questions to surface technical and business constraints. This guides the prioritization of architectural decision drivers and clarifies trade-off patterns.

Can I use this for reviewing existing ADRs?▼

Yes, you can use it for ADR reviews and governance. It helps align stakeholders by evaluating whether existing architectural documentation properly captures driver categories, quality attributes, and trade-off patterns.

When do I need to formally document architectural decision drivers?▼

You need to formally document architectural decision drivers when creating a new ADR or reviewing one. This ensures the forces shaping trade-offs and prioritization across business and technical concerns are well-justified.

Related Skills

Explore More Software Engineering Skills→
mwathibenmwathiben

product-requirements

Convert vague product ideas into testable PRDs with a 100-point quality framework.

Community
Advanced
keshavraj936keshavraj936

architecture

Guide architectural decisions with requirements analysis, trade-off evaluation, and ADR documentation.

Community
Advanced
xenitV1xenitV1
132

architecture

Systematize requirements analysis and ADR documentation for architecture decisions.

Community
Basic
aget-frameworkaget-framework
11

aget-assess-tradeoffs

Evaluate architectural options against quality attributes and reversibility.

Official
Intermediate