convention-adr

Document architecture decisions with a standardized ADR template.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/sunLeee/optimization --skill convention-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convention-adr
Source: https://github.com/sunLeee/optimization/tree/main/.claude/skills/process/adr
Command: npx skills add https://github.com/sunLeee/optimization --skill convention-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions that are hard to reverse require explicit ADR documentation to preserve context and rationale when changes occur.

Core Features & Use Cases

  • ADR standard format captures context, decision, and consequences to guide future work
  • Provides a consistent template and lifecycle for architectural choices across projects
  • Example: create ADR-001 to document choosing a database schema approach and its trade-offs

Quick Start

Create a new ADR document following the ADR-{number} format to capture a major architectural decision.

Frequently Asked Questions about convention-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) documents architectural choices to preserve context and rationale. You need an ADR for architecture decisions that are hard to reverse and require explicit governance across project lifecycle stages.

How do I document architecture decisions using a standard ADR template?

To document architecture decisions, create an ADR document following the ADR-{number} format. Capture the context, decision, and consequences to standardize architectural choices and guide future work across teams.

What should be included in an ADR for software systems governance?

An ADR for software systems governance should include the context, decision, and consequences. This standardized format captures rationale and trade-offs, ensuring consistent ADR documentation across projects and teams.

Does this ADR template work for documenting database schema decisions?

Yes, the ADR template works for documenting database schema decisions. You can create ADR-001 to capture the context, decision, and consequences of choosing a database schema approach and its trade-offs.

Why does my team need standardized ADR documentation for architecture decisions?

Your team needs standardized ADR documentation because architecture decisions that are hard to reverse require explicit records. ADRs preserve context and rationale when changes occur, maintaining governance across lifecycle stages.

Can I use ADRs to capture design decisions across different projects and teams?

Yes, you can use ADRs to capture decisions across projects, teams, and lifecycle stages. The standardized ADR template enforces consistent documentation of context, decision, and consequences for software systems.