skills.rest
ronniepinnell
ronniepinnellCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

adr

Document architectural decisions with Context, Options, Decision, and Consequences.

Updated Aug 27, 2026
Search Tags:#architecture#documentation#adr#decision#governance#design-review
One-click install
npx skills add https://github.com/ronniepinnell/benchsight --skill adr-ronniepinnell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/ronniepinnell/benchsight/tree/main/.claude/skills/adr
Command: npx skills add https://github.com/ronniepinnell/benchsight --skill adr-ronniepinnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions often lack formal capture, causing misalignment and rework. ADR provides a structured way to record the rationale, options, and consequences for critical design choices.

Core Features & Use Cases

  • Structured decision records for major architectural choices.
  • Clear rationale, trade-offs, and consequences to guide future work.
  • Centralized documentation in docs/ARCHITECTURE_DECISIONS.md, searchable for governance and onboarding.

Quick Start

Present the ADR to the Architecture Team and record the decision in ARCHITECTURE_DECISIONS.md.

Frequently Asked Questions about adr

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

FAQPage Schema
What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) is a formal document capturing the context, options, decision, and consequences of a significant design choice. You need an ADR when architectural decisions lack formal capture, causing team misalignment and rework.

How do I document architectural trade-offs and design decisions?▼

You document architectural trade-offs by producing a formal Architecture Decision Record that details the Context, Options, Decision, and Consequences. This structured record is then saved in docs/ARCHITECTURE_DECISIONS.md to guide future work.

What is the best way to ensure traceable governance for architecture decisions?▼

The best way to ensure traceable governance is to maintain centralized ADR documentation in docs/ARCHITECTURE_DECISIONS.md and log the new decision via the intel.decisions interface, providing searchable historical context for onboarding.

How do I present architecture decisions to an architecture team?▼

You present architecture decisions to an architecture team by generating a structured ADR that outlines the rationale and consequences, then formally presenting the record to the team for review before logging it.

Does this approach to architecture documentation require a database connection?▼

Yes, logging the new architectural decision requires a connection to Supabase to record the entry via the intel.decisions interface, while the primary documentation is stored locally in the docs directory.

Related Skills

Explore More Software Engineering Skills→
bkywksjbkywksj
309

tech-decision

Document technology choices and rationale in Architecture Decision Records with enforced templates.

Community
Intermediate
sddevelopment-besddevelopment-be
13

review

Assess architectural decisions and code quality to generate a structured review document with ADR compliance and security checks.

Official
Advanced
0xHoneyJar0xHoneyJar
2

auditing-security

Audit code, deployment, and sprint artifacts for security and quality gaps.

Official
Advanced
xenitV1xenitV1
132

architecture

Systematize requirements analysis and ADR documentation for architecture decisions.

Community
Basic