adr

Create, list, and update Architecture Decision Records in docs/adrs/.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kagenti/humr --skill adr-kagenti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/kagenti/humr/tree/main/.agents/skills/adr
Command: npx skills add https://github.com/kagenti/humr --skill adr-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tracks Architecture Decision Records (ADRs) in docs/adrs/. Creates, lists, and updates ADRs following project conventions. TRIGGER when: user wants to record, review, or update an architectural decision. argument-hint: "[what you'd like to do]"

Core Features & Use Cases

  • Create ADRs following project conventions with proper numbering.
  • Update ADRs and reflect status changes (Proposed to Accepted) and maintain an index.
  • Review ADRs to ensure consistency and ownership across the codebase.

Quick Start

Create a new ADR in docs/adrs/ following the ADR conventions and update the index.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I track Architecture Decision Records across my projects?

Track Architecture Decision Records by storing them in the docs/adrs/ directory, which enforces naming conventions, index updates, and owner assignments to maintain consistency across projects.

How do I update the status of an ADR from Proposed to Accepted?

Update ADR status by transitioning records from Proposed to Accepted, which automatically reflects the status change and maintains the project's ADR index to keep documentation current.

What is the best way to enforce naming conventions for architectural decision records?

Enforce ADR naming conventions by using a tracking system that validates record creation in the docs/adrs/ directory, ensuring proper numbering and consistent architectural decision documentation.

How do I assign ownership for architectural decisions in my codebase?

Assign ADR ownership by tracking owner assignments during record creation and review, ensuring team members are accountable for architectural decisions across the codebase.

Can I review existing ADRs to ensure consistency and ownership across projects?

Review ADRs by listing and validating existing records in the docs/adrs/ directory, checking for consistent naming, proper ownership assignments, and accurate status tracking.

When do I need to create an Architecture Decision Record?

Create an Architecture Decision Record when teams need to formally record, review, or update architectural decisions, following project conventions with proper numbering and index maintenance.