architecture-decision-records

Document architecture decisions with structured ADR records capturing context, options, and consequences.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill architecture-decision-records-jhabbig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/plugins/wshobson/documentation-generation/skills/architecture-decision-records
Command: npx skills add https://github.com/Jhabbig/Habbig --skill architecture-decision-records-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams document important architectural choices in a consistent way, so future readers can understand what was decided, why it was chosen, and what trade-offs were accepted.

Core Features & Use Cases

  • ADR Writing: Create clear, durable decision records for technology selection, integration patterns, and system design choices.
  • Decision Review: Summarize past decisions, track status changes, and distinguish accepted, deprecated, rejected, and superseded records.
  • Governance Support: Establish a lightweight process for proposing, reviewing, approving, and maintaining architecture decisions across a project.
  • Use Case: A team choosing between PostgreSQL, MySQL, and MongoDB can use this Skill to produce a structured ADR that captures context, rationale, and consequences.

Quick Start

Use this skill to draft an ADR for a major technical decision in your project, including the context, options considered, final choice, and resulting consequences.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema
How do I write an architecture decision record for technology selection?

To write an architecture decision record, document the context, options considered, final decision, and consequences. This Skill generates structured ADRs with review-friendly formatting, ensuring technical choices for technology selection are captured clearly for future readers.

What is the best way to document system design trade-offs for technical governance?

Documenting system design trade-offs for technical governance requires structured records that capture accepted decisions and their rationale. This Skill applies ADR or RFC style templates to establish a lightweight process for proposing, reviewing, and maintaining architecture decisions across a project.

How do I track the status of past architecture decisions like deprecated or superseded records?

Tracking the status of past architecture decisions involves summarizing historical records and distinguishing accepted, deprecated, rejected, and superseded entries. This Skill supports decision review by applying clear status tracking to maintain an accurate history of technical governance.

Can I use RFC style templates for deprecation planning in software projects?

Yes, you can use RFC style templates for deprecation planning in software projects. This Skill documents architecture decisions using ADR or RFC formats that capture context and consequences, applying to deprecation planning and historical decision review with consistent formatting.

When do I need an ADR for my software project?

You need an ADR when making major technical decisions involving system design choices, integration patterns, or technology selection. This Skill helps establish a lightweight governance process to propose, review, and approve architecture decisions, ensuring durable records of accepted trade-offs.