skills.rest
polikeiji
polikeijiCOMMUNITY
Explore all skills by this author →
GitHub

adr

Write architecture decision records with YAML frontmatter and option analysis.

Updated Jun 5, 2026
Search Tags:#architecture#adr#technical documentation#trade-offs#decision records#engineering standards
One-click install
npx skills add https://github.com/polikeiji/skills --skill adr-polikeiji
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/polikeiji/skills/tree/main/skills/adr
Command: npx skills add https://github.com/polikeiji/skills --skill adr-polikeiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams document important architecture decisions so the reasoning, trade-offs, and outcomes behind technical choices are preserved instead of lost in chat or memory.

Core Features & Use Cases

  • Creates structured ADRs with required frontmatter, status tracking, and clear file naming.
  • Surveys existing decision records before writing so new ADRs fit into the current history.
  • Guides users through motivation, decision drivers, options, consequences, and links.
  • Keeps the ADR index updated when records are added, superseded, or deprecated.
  • Use it when you need to record why a technology, design approach, or engineering standard was chosen.

Quick Start

Ask the adr skill to help you write an ADR for a technical decision and provide the problem, options considered, and final choice.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I write an architecture decision record for a new technology choice?▼

An architecture decision record captures technical choices by documenting motivation, decision drivers, options, and consequences. This skill generates ADRs with YAML frontmatter and sequential numbering in docs/adrs/.

What is the best way to document technical trade-offs for engineering standards?▼

Documenting technical trade-offs requires recording the considered options and their consequences. This skill creates structured ADRs that capture the reasoning behind engineering standards so the context is preserved for the team.

How do I maintain an ADR index when records are superseded or deprecated?▼

Maintaining an ADR index involves tracking status changes and updating the central log. This skill automatically updates the index when records are added, superseded, or deprecated, ensuring decision history remains consistent.

Does writing architecture decision records require specific frontmatter or file formats?▼

Writing architecture decision records requires YAML frontmatter for status tracking and metadata. This skill enforces required frontmatter, clear file naming, and sequential numbering to keep records organized.

When do I need to create an ADR for system design decisions?▼

You need to create an ADR when making a significant system design choice or technology selection. This skill surveys existing decision records first to ensure new ADRs fit into the current history.

Related Skills

Explore More Software Engineering Skills→
FoundationForgeFoundationForge

architecture

Create and evaluate Architecture Decision Records with structured context and trade-offs.

Official
Advanced
levnikolaevichlevnikolaevich
534

ln-332-task-reviewer

Reviews completed development tasks for quality and standards compliance.

Community
Intermediate
subroh0508subroh0508
18

adr-author

Drafts numbered ADRs and updates the index with cross-links and eligibility checks.

Community
Advanced
AmidVoshakulAmidVoshakul

architecture-decision-records

Standardize creation and maintenance of Architecture Decision Records with templates.

Community
Intermediate