architecture-decision-recorder

Capture architectural decisions and rationale in standardized ADR documents.

7|2|Updated Nov 9, 2025

Search Tags:#documentation #software design #adr #rationale #tradeoffs #architecture decision records

Ready to run

npx skills add https://github.com/Prompt-or-Die-Labs/hyper-forge --skill architecture-decision-recorder-prompt-or-die-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-recorder
Source: https://github.com/Prompt-or-Die-Labs/hyper-forge/tree/main/.claude/skills/architecture-decision-recorder
Command: npx skills add https://github.com/Prompt-or-Die-Labs/hyper-forge --skill architecture-decision-recorder-prompt-or-die-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents architectural decisions from being lost, duplicated, or debated repeatedly by capturing tradeoffs and rationale in a consistent ADR format.

Core Features & Use Cases

ADRs as a decision history: Create immutable records of significant architectural decisions, including context, decision, rationale, consequences, and alternatives.
Team alignment and traceability: Link related ADRs and keep stakeholders aligned on why choices were made.
Operational consistency: Use a standardized template to ensure each ADR includes implementation actions, risks, and references.
Common use case: When migrating or adopting a new subsystem, document the driving constraints, options considered, and the expected positive/negative consequences to guide future work.

Quick Start

Create a new ADR by following the ADR template to document a recent technology choice, including context, decision, rationale, consequences, alternatives, and a list of implementation action items.

Frequently Asked Questions about architecture-decision-recorder

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

FAQPage Schema

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

Architecture decision records prevent lost or duplicated decisions by providing a standardized template. ADRs ensure team alignment by documenting decision makers, context, rationale, consequences, and alternatives for significant software design choices.

How do I write an ADR document for a new technology choice?▼

To write an ADR document, use a standardized template to capture the title, date, status, and decision makers. Include sections for context, the decision itself, rationale, consequences, alternatives considered, implementation action items, and references for complete traceability.

What should be included in architecture decision records to ensure team alignment?▼

Architecture decision records should include required metadata like title, date, status, and decision makers. Add sections for context, decision rationale, alternatives, consequences, implementation actions, and references to link related ADRs and maintain stakeholder alignment over time.

Does this ADR format work for documenting system migration constraints and tradeoffs?▼

Yes, this ADR format works for system migrations by documenting driving constraints, options considered, and expected positive or negative consequences. It creates an immutable record that guides future implementation work and maintains operational consistency across the team.

When should I not use an architecture decision record?▼

Architecture decision records should not be used for trivial implementation details that lack significant tradeoffs. Reserve ADRs for significant software design choices where documenting context, constraints, alternatives, and rationale provides durable value for future teams.