architecture-decision-records

Document architecture decisions with context, outcomes, consequences, and alternatives.

Updated May 16, 2026
One-click install
npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill architecture-decision-records-p-o-ke-nae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory/tree/main/.github/skills/architecture-decision-records
Command: npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill architecture-decision-records-p-o-ke-nae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams capture important technical decisions in a consistent, reviewable format so future contributors can understand the context, trade-offs, and outcomes behind architecture choices.

Core Features & Use Cases

  • Decision Documentation: Record the problem, decision, consequences, and alternatives for significant technical changes.
  • Decision Lifecycle Management: Track status changes such as proposed, accepted, deprecated, and superseded across the ADR history.
  • Team Alignment: Use templates and review checklists to standardize how engineers discuss and approve architecture choices.
  • Use Case: A team choosing a database, deprecating a technology, or establishing an integration pattern can use this Skill to create a clear ADR that stays useful long after implementation.

Quick Start

Ask for a new ADR draft that captures the decision context, considered options, final choice, consequences, and review checklist in the project’s preferred format.

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 architecture trade-offs for a new technology selection?

Document architecture trade-offs by recording the problem context, considered options, final choice, and consequences. This ensures future contributors understand the rationale behind significant technical changes long after implementation.

What is an architecture decision record and when do I need one?

An architecture decision record captures important technical decisions in a consistent, reviewable format. You need one for technology selection, deprecation planning, and integration patterns to maintain team alignment and historical context.

How do I track the lifecycle status of an architecture decision?

Track architecture decision lifecycle status using state markers like proposed, accepted, deprecated, and superseded. This status tracking keeps the ADR history accurate and maintainable as engineering decisions evolve over time.

Can I standardize how my engineering team reviews and approves architecture choices?

Standardize engineering reviews by applying ADR templates and review checklists. This structured approach ensures consistent documentation of decision outcomes and alternatives, aligning the team on architecture choices.

What is the best way to plan the deprecation of an existing technology?

Plan technology deprecation by drafting an ADR that captures the decision context, alternatives, and consequences. This establishes a clear, reviewable record of why the technology is being deprecated and what replaces it.