architecture-decision-records

Records architectural decisions with context, alternatives, rationale, and consequences in a structured format.

4|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/aaaa47080/stock_agent --skill architecture-decision-records-aaaa47080
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/aaaa47080/stock_agent/tree/main/.opencode/skills/architecture-decision-records
Command: npx skills add https://github.com/aaaa47080/stock_agent --skill architecture-decision-records-aaaa47080

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADRs solve the problem of undocumented architectural decisions and eroding context by capturing decisions, rationales, and trade-offs in a structured, searchable format.

Core Features & Use Cases

  • Structured ADR format with sections for Context, Decision, Alternatives considered, and Consequences.
  • Workflow for creating, reviewing, and updating ADRs with numbering and lifecycle states.
  • Improves governance, onboarding, and long-term maintenance by preserving rationale behind design choices.

Quick Start

Create a new ADR document describing a significant architectural decision, including the problem context, the chosen decision, considered alternatives, and the expected consequences.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema
How do I document architectural decisions to prevent context drift?

You document architectural decisions by creating an Architecture Decision Record that captures the context, chosen decision, considered alternatives, and consequences to preserve rationale and prevent drift.

What is the best way to structure trade-offs for framework and database selections?

The best way to structure trade-offs is using an ADR format with dedicated sections for Context, Decision, Alternatives considered, and Consequences, ensuring design choices are searchable.

How do I manage the lifecycle of an architectural decision record?

You manage the ADR lifecycle by applying an incremental numbering scheme and tracking lifecycle states during design reviews and planning sessions to maintain governance over time.

When do I need to create an architecture decision record?

You need to create an architecture decision record during design reviews and planning sessions when making significant choices involving frameworks, databases, or interfaces to preserve trade-off rationale.

Can I use ADRs to improve onboarding and long-term maintenance?

Yes, you can use ADRs to improve onboarding and long-term maintenance by preserving the rationale behind design choices in a structured, searchable format that prevents eroding context.