architectural-decision-record

Create, extract, and convert Architectural Decision Records to standard templates.

198|19|Updated May 7, 2026
One-click install
npx skills add https://github.com/testdouble/han --skill architectural-decision-record
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architectural-decision-record
Source: https://github.com/testdouble/han/tree/main/han-core/skills/architectural-decision-record
Command: npx skills add https://github.com/testdouble/han --skill architectural-decision-record

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions are critical for guiding engineering work, but creating, extracting, and converting ADRs into a consistent, queryable format is often manual and error-prone.

Core Features & Use Cases

  • Create ADRs from scratch using the standard ADR template.
  • Extract ADRs from existing documentation and convert them into ADR format.
  • Update ADR status, references, and evidence linkage to maintain traceability.

Quick Start

Create a new ADR document for the latest architecture decision using the ADR template.

Frequently Asked Questions about architectural-decision-record

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

FAQPage Schema
What is an Architectural Decision Record and what fields should it include?

To create an ADR from scratch, you apply a standard template that enforces required fields: Context, Decision Drivers, Considered Options, Decision, Consequences, and Notes, ensuring every new architecture decision is consistently documented.

How do I convert existing documentation into ADR format?

You can extract architectural decisions from existing project documentation and convert them into standard ADR format. The process maps the content to the required template fields and links relevant evidence to maintain traceability.

Can I update the status and references of an existing ADR?

Yes, you can update ADR status, references, and evidence linkage across a project. This maintains traceability over time as architectural decisions evolve and new linked evidence becomes available.

What is the best way to maintain a history of architecture decisions?

The best way to maintain architecture decision histories is using standard ADR templates that enforce consistent fields and support linked evidence. This converts static documentation into living, maintainable records with clear traceability.

Does this ADR workflow support linking external evidence and references?

Yes, the ADR workflow supports linked evidence and references via provided templates. This ensures that every architectural decision recorded maintains traceability back to its supporting project documentation and context.