review-adr

Review ADR YAML frontmatter and enforce lifecycle status transitions.

30|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/atomicinnovation/accelerator --skill review-adr-atomicinnovation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-adr
Source: https://github.com/atomicinnovation/accelerator/tree/main/skills/decisions/review-adr
Command: npx skills add https://github.com/atomicinnovation/accelerator --skill review-adr-atomicinnovation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the review and lifecycle management of Architecture Decision Records (ADRs), ensuring decisions are high quality, traceable, and adhere to an append-only immutability model so that accepted records remain unchanged except for sanctioned status transitions.

Core Features & Use Cases

  • Quality assessment: Performs a structured checklist-style review covering context, decision drivers, options analysis, consequences, and overall clarity.
  • Lifecycle enforcement: Reads ADR frontmatter status and enforces permitted transitions (proposed → accepted/rejected; accepted → deprecated) while preventing content edits on immutable statuses.
  • Interactive workflows: Guides the reviewer through selection, suggested revisions, acceptance, rejection with reason, and deprecation flows, and updates frontmatter and in-body status lines accordingly.
  • Use case: A team member presents a proposed ADR for review; the skill evaluates completeness, suggests improvements, and either accepts it as immutable, rejects with rationale, or revises the document and prompts for re-review.

Quick Start

Review the ADR at meta/decisions/ADR-0001-use-jujutsu.md and produce a structured assessment and an action to accept, reject, or request revisions.

Frequently Asked Questions about review-adr

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

FAQPage Schema
How do I review architecture decision records for completeness and quality?

To review architecture decision records, evaluate the document's context, decision drivers, options analysis, consequences, and overall clarity using a structured checklist to ensure decisions are traceable and well-documented.

What are the permitted status transitions for ADR lifecycle management?

Permitted ADR status transitions follow an append-only immutability model: proposed can move to accepted or rejected, and accepted can move to deprecated, while preventing content edits on immutable statuses.

How do I deprecate an accepted ADR without violating immutability rules?

To deprecate an accepted ADR, update the YAML frontmatter and in-body status fields to deprecated while keeping the original decision content unchanged, ensuring the append-only immutability model is maintained.

Can I use shell scripts to gather contextual data during an ADR review?

Yes, you can invoke configured shell scripts during an ADR review to gather contextual data needed for evaluating, accepting, rejecting, or revising architectural decisions in your repository's decisions directory.

What is the best way to manage ADR lifecycle status in a repository decisions directory?

The best way to manage ADR lifecycle status is to read YAML frontmatter and body content, validate the status against immutability rules, and update frontmatter and in-body status fields for permitted transitions during planning and design workflows.

Why should accepted architecture decision records remain unchanged?

Accepted architecture decision records should remain unchanged to enforce an append-only immutability model, ensuring historical decisions are traceable and reliable except for sanctioned status transitions like deprecation.