skills.rest
levnikolaevich
levnikolaevichCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ln-74-architecture-decision-recorder

Records one architecture decision with context, alternatives, tradeoffs, and consequences in an ADR document.

556|83|Updated Oct 24, 2025
Search Tags:#ADR#decision tracking#Documentation#architecture decision record#tradeoffs#supersession#Software Architecture
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-74-architecture-decision-recorder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ln-74-architecture-decision-recorder
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/plugins/architecture-suite/skills/ln-74-architecture-decision-recorder
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-74-architecture-decision-recorder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Significant architecture choices often lose their rationale over time, leaving future maintainers unable to understand why a system was built a certain way. This Skill captures one architecturally significant decision in a durable, reviewable record before that context disappears.

Core Features & Use Cases

  • Structured ADR Creation: Writes a decision record with title, status, deciders, context, drivers, alternatives, consequences, and review triggers, following the repository's existing ADR convention or a default docs/architecture/decisions/NNNN-<slug>.md path.
  • Alternatives Evaluation: Compares the status quo and materially different options against the same drivers, recording why each rejected option loses in this context.
  • Supersession and Status Governance: Defaults new records to Proposed, requires explicit authority for Accepted, and links superseded records bidirectionally without erasing history.
  • Use Case: After choosing PostgreSQL over DynamoDB for a new service, use this Skill to document the drivers, rejected alternatives, accepted costs, and conditions that would trigger revisiting the choice.

Quick Start

Record an architecture decision for our choice of event-driven messaging over synchronous REST between the billing and notification services.

Frequently Asked Questions about ln-74-architecture-decision-recorder

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

FAQPage Schema
How do I write an architecture decision record (ADR)?▼

An ADR captures one decision with its context, drivers, considered alternatives, the chosen option, and consequences. This Skill writes the record following your repository's existing convention or a default numbered path, defaulting the status to Proposed until explicitly accepted.

When should I create an architecture decision record?▼

Create an ADR when a choice is architecturally significant: it affects system boundaries, contracts, data, security, operations, or cost in ways that are hard to reverse. It is not meant for broad design work, audits, or implementation tasks.

How do I supersede an existing ADR without losing history?▼

Mark the old record as Superseded and link both records in both directions while preserving the original content. Never renumber, overwrite, or delete historical records; the new record gets the next unused monotonic number.

Can an ADR be marked Accepted automatically?▼

No. A new record defaults to Proposed, and Accepted is only assigned after explicit confirmation from an authorized decision-maker. Retrospective records created after implementation must be labeled as such, not presented as prior approval.

What are the limitations of recording decisions as ADRs?▼

An ADR captures one decision only; independent decisions with different drivers or lifecycles need separate records. The Skill returns BLOCKED for ambiguous scope, unsafe numbering, conflicting ownership, or when no writable destination exists.

Related Skills

Explore More Software Engineering Skills→
sachinnair90sachinnair90

architectural-proposals

Write evidence-based architectural proposals with problem statements, risks, and scope.

Community
Advanced
avgarciaavgarcia

disparador-checker

Track documented triggers to prevent premature reopening of deferred decisions.

Community
Intermediate
Pabloprogramador23Pabloprogramador23

reversa-designer

Plan and execute a two-phase migration design from legacy to modern architecture.

Community
Advanced
rvdbreemenrvdbreemen
199

doc-coauthoring

Guide collaborative documentation through staged drafting and reader-testing checks.

Community
Advanced