yak-adr

Create, supersede, amend, and index Architecture Decision Records in docs/adr.

3|3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/mrdavidlaing/yakthang --skill yak-adr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: yak-adr
Source: https://github.com/mrdavidlaing/yakthang/tree/main/skills/yak-adr
Command: npx skills add https://github.com/mrdavidlaing/yakthang --skill yak-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture, organize, and cross-reference Architecture Decision Records (ADRs) within a project, eliminating ambiguity and ensuring decisions are documented and traceable over time.

Core Features & Use Cases

  • ADR lifecycle management: create, supersede, amend, and maintain a consistent ADR history.
  • Documentation discipline: ADRs stored under docs/adr with a standardized naming and indexing scheme.
  • Cross-referencing and auditing: link related ADRs and maintain a clear decision trail for future maintainers.

Quick Start

Create your first ADR by documenting a decision using the Create workflow and updating the ADR index.

Frequently Asked Questions about yak-adr

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

FAQPage Schema
How do I document and govern architectural decisions in a software project?▼

Automate and standardize the capture of Architecture Decision Records (ADRs) by creating them within a docs/adr directory, utilizing a 4-digit numbering scheme, statuses, and a README index to ensure decisions remain traceable over time.

What is the best way to manage the lifecycle of an Architecture Decision Record?▼

Manage the Architecture Decision Record lifecycle through a document-driven workflow enabling you to create, supersede, amend, and index ADRs, maintaining a consistent and auditable decision history across multiple components.

How do I supersede or amend an existing ADR without losing the historical context?▼

Supersede or amend an existing ADR by using the governance workflow to cross-reference related records, ensuring the historical decision trail remains clear for future maintainers while updating the current architectural status.

Does this ADR workflow require any specific dependencies or external components?▼

This ADR workflow requires no external dependencies or components, operating entirely through a simple, document-driven workflow to maintain architectural governance and documentation discipline within your project.

When should I use a document-driven ADR workflow for architectural governance?▼

Use a document-driven ADR workflow when making architectural decisions across multiple components, specifically when you need to eliminate ambiguity, enforce documentation discipline, and ensure decisions are cross-referenced and traceable.