architecture-decision-records

Capture architectural decisions as structured ADR documents with context and alternatives.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/himanshu231204/AI_Research_agent --skill architecture-decision-records-himanshu231204
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/himanshu231204/AI_Research_agent/tree/main/.opencode/skills/architecture-decision-records
Command: npx skills add https://github.com/himanshu231204/AI_Research_agent --skill architecture-decision-records-himanshu231204

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions are frequently lost in informal channels like Slack threads, PR comments, or team memory, leaving future developers without context for why the codebase is structured the way it is.

Core Features & Use Cases

  • Automated ADR Generation: Detects decision moments in conversation and produces structured Architecture Decision Record documents with all required sections including context, alternatives, and rationale.
  • ADR Index Maintenance: Automatically manages a searchable index of all ADRs stored in a dedicated docs/adr/ directory for quick reference.
  • Use Case: When your team chooses between using Redis or Memcached for caching, this skill creates a documented ADR outlining trade-offs, rejected alternatives, and the final rationale so new team members can understand the choice without tracking down original decision-makers.

Quick Start

Use the architecture-decision-records skill to document the decision to adopt LangGraph for multi-agent orchestration in the research agent, including all evaluated alternatives and their trade-offs.

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 preserve technical rationale?

Document architectural decisions by capturing context, rejected alternatives, and rationale in structured Architecture Decision Record (ADR) documents. This preserves institutional knowledge and prevents context loss for future development teams.

When do I need to create an Architecture Decision Record?

Create an Architecture Decision Record during technology selection, architecture pattern evaluation, API design choices, and infrastructure trade-off discussions across both planning and implementation phases to ensure traceable codebase governance.

How do I maintain an index of ADRs for quick reference?

Maintain a searchable ADR index by automatically managing records stored in a dedicated docs/adr/ directory. This allows developers to quickly reference past architectural decisions without tracking down original decision-makers.

What is the best way to log trade-off analysis for software documentation?

Log trade-off analysis by generating structured ADR documents that outline evaluated alternatives, consequence analysis, and final rationale, ensuring new team members understand the codebase design choices.

Can I use ADRs for infrastructure trade-off discussions and API design choices?

Yes, ADRs apply to infrastructure trade-off discussions and API design choices. They document the decision context and lifecycle tracking required for comprehensive codebase governance and technical rationale preservation.