architecture-decision-records

Document significant technical decisions as architecture decision records with context and rationale.

672|104|Updated Apr 10, 2026

Search Tags:#documentation #adr #architecture decisions #decision records #technical decisions #tradeoffs

Ready to run

npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill architecture-decision-records-spencerpauly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/architecture-decision-records
Command: npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill architecture-decision-records-spencerpauly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you record important technical choices before the reasons behind them are forgotten, making future maintenance, onboarding, and team alignment much easier.

Core Features & Use Cases

Decision Documentation: Turn major architecture, tooling, and process choices into concise ADRs.
Tradeoff Tracking: Capture the options considered, why each mattered, and the final rationale.
Long-Term Reference: Keep a durable record for decisions that are hard to reverse or likely to be revisited later.
Use Case: When choosing a database, framework, auth strategy, or build tool, use this Skill to create a structured decision record that the whole team can reference later.

Quick Start

Write an architecture decision record for the database choice in docs/decisions using the standard ADR structure.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema

What is an architecture decision record and when should I document technical tradeoffs?▼

An architecture decision record (ADR) documents significant technical choices by capturing context, options considered, rationale, and consequences. You should document tradeoffs for hard-to-reverse engineering choices affecting multiple system parts that may be revisited months later.

How do I write an architecture decision record for a database or framework choice?▼

To write an architecture decision record, apply a structured ADR template to document the context, options considered, rationale, and consequences of your database or framework choice. Use sequential file naming and concise, review-ready decision writing for long-term team reference.

What's the best way to track technical decisions and rationale for future onboarding?▼

The best way to track technical decisions for onboarding is creating architecture decision records that capture context, options considered, and rationale. This provides a durable, long-term reference record that makes future maintenance and team alignment much easier.

Do I need a specific ADR template structure to document architecture decisions?▼

Yes, documenting architecture decisions requires a structured ADR template to ensure context, options considered, rationale, and consequences are consistently captured. Sequential file naming and concise review-ready writing are also needed for a durable long-term reference.

Can I use architecture decision records for process and tooling choices, not just major architecture changes?▼

Yes, you can use architecture decision records for process and tooling choices, not just major architecture changes. Any significant technical decision with tradeoffs that is hard to reverse or likely to be revisited later is a candidate for an ADR.