architecture-decision-records

Q: How do I install architecture-decision-records?

Run npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill architecture-decision-records in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/architecture-decision-records/ (personal) or .claude/skills/architecture-decision-records/ (project).

by spencerpaulyCode Quality & Workflow

Document technical decisions as Architecture Decision Records (ADRs) with context, options considered, and rationale.

Installs: 454
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

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

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads architecture-decision-records automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Architecture Decision Records

Document significant technical decisions so future you (and your team) understands why choices were made.

When to Write an ADR

Write one when you're making a decision that:

Is hard to reverse later
Affects multiple parts of the system
Involves tradeoffs between valid options
Will be questioned by someone in 6 months

Examples: choosing a database, adopting a framework, changing auth strategy, restructuring the API, adding a build tool.

Template

Create files in docs/decisions/ (or adr/) with sequential numbering:

# ADR-001: Use PostgreSQL for primary database

## Status

Accepted | Proposed | Deprecated | Superseded by ADR-XXX

## Date

2026-04-10

## Context

What is the problem or situation that requires a decision?
Include constraints, requirements, and forces at play.

## Options Considered

### Option A: PostgreSQL
- Pros: ACID compliance, JSON support, mature ecosystem, free
- Cons: Requires managing connections, vertical scaling limits

### Option B: MongoDB
- Pros: Flexible schema, horizontal scaling
- Cons: No transactions across collections, eventual consistency issues

### Option C: PlanetScale (MySQL)
- Pros: Serverless, branching, managed
- Cons: Vendor lock-in, no foreign keys in their branching model

## Decision

We chose **PostgreSQL** because:
1. Our data is relational — users, teams, projects with clear relationships
2. We need ACID transactions for billing operations
3. JSON columns give us schema flexibility where needed
4. Prisma/Drizzle have excellent Postgres support

## Consequences

- We need to manage connection pooling (use PgBouncer or Prisma's built-in pool)
- Migrations must be backwards-compatible for zero-downtime deploys
- We accept vertical scaling limits and will shard later if needed

Workflow

Identify the decision being made
Research the options (at least 2-3 alternatives)
Write the ADR using the template
Review with the team (PR or discussion)
Merge as accepted
Reference from code comments when relevant: // See ADR-001

File Naming

docs/decisions/
├── 001-use-postgresql.md
├── 002-adopt-trpc-over-rest.md
├── 003-switch-to-pnpm.md
└── template.md

Tips

Keep ADRs short — 1-2 pages max
Write them in the present tense ("We choose X" not "We chose X")
It's OK to write an ADR after the fact if you forgot to write one during the decision
Superseded ADRs should link to their replacement, not be deleted
ADRs are not design docs — they capture the decision, not the full design

FAQ

What does the architecture-decision-records skill do?

Document technical decisions as Architecture Decision Records (ADRs) with context, options considered, and rationale.

How do I install architecture-decision-records?

Run npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill architecture-decision-records in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/architecture-decision-records/ (personal) or .claude/skills/architecture-decision-records/ (project).

Which AI agents can use architecture-decision-records?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is architecture-decision-records safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains architecture-decision-records?

It is published by spencerpauly in spencerpauly/awesome-cursor-skills. It has 454 recorded installs.