adr

Creates and updates Korean Architecture Decision Records in docs/decisions with numbered Markdown files.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/kubrickcode/cine-mirror --skill adr-kubrickcode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/kubrickcode/cine-mirror/tree/main/.agents/skills/adr
Command: npx skills add https://github.com/kubrickcode/cine-mirror --skill adr-kubrickcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Architecturally significant decisions often get lost in chat history or scattered analysis documents, making it hard for teams to recall why a choice was made. This Skill records those decisions as concise, numbered Architecture Decision Records (ADRs) in a version-controlled docs/decisions/ directory. ## Core Features & Use Cases - ADR Creation: Generates zero-padded, sequentially numbered ADR files (e.g., 0001-use-postgres.md) written in Korean using a structured template covering context, options, decision, and trade-offs. - Supersede Handling: Scans existing ADRs to detect duplicates and updates the status of superseded records, keeping the decision history consistent. - Distillation from Analysis: Extracts only the decision and rationale from analysis documents or conversation context instead of duplicating source material. - Use Case: After a design discussion about switching from REST to gRPC, invoke the Skill to produce a one-page Korean ADR documenting the options considered, the accepted trade-offs, and links to related PRs. ## Quick Start Ask the assistant to create an ADR for the decision to adopt gRPC for internal service communication.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I create an Architecture Decision Record for my project?▼

Invoke the Skill with a decision topic, and it generates a numbered Markdown ADR in docs/decisions/ using a structured template. The record covers context, decision factors, considered options with pros and cons, the final decision, and accepted trade-offs.

When should I write an ADR instead of regular documentation?▼

Write an ADR when a decision meets the PRICE criteria: Policy, Reversibility, Impact, Constraint, or Exception. Trivial or easily reversible choices are explicitly excluded to keep the decision log meaningful.

Can an ADR supersede or replace an existing decision record?▼

Yes. The Skill scans existing ADRs by slug to detect related records, then marks the old ADR as superseded while the new record references it via a supersedes field. This preserves the full decision history.

What language and format do the generated ADR files use?▼

ADRs are written in Korean with English technical terms allowed in parentheses. Files use zero-padded four-digit numbering (0001, 0002) and a fixed Markdown template with YAML frontmatter containing name, description, status, and date.

What are the limitations of automated ADR generation?▼

The Skill distills decisions from conversation or analysis documents, so it depends on the quality of available context. It intentionally keeps records under one page and will not reproduce full analysis documents, so deep technical detail stays in the source material.