adr-review

Review ADR implementations against codebases and generate structured reports.

8|2|Updated Jun 4, 2024
One-click install
npx skills add https://github.com/cmd-llm/cllm --skill adr-review-cmd-llm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr-review
Source: https://github.com/cmd-llm/cllm/tree/main/.claude/skills/adr-review
Command: npx skills add https://github.com/cmd-llm/cllm --skill adr-review-cmd-llm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill performs post-implementation reviews of Architecture Decision Records (ADRs) by comparing the documented decision against the actual implementation.

Core Features & Use Cases

  • Identify the ADR to review and locate it in docs/decisions/
  • Extract key sections: Decision Outcome, Confirmation Criteria, Test Expectations, Dependencies, Timeline, Risk, AI Extensions
  • Inspect the actual codebase to verify implementation against the ADR
  • Update the ADR Feedback Log with findings, gaps, and lessons
  • Generate a structured ADR Review Report summarizing status and evidence

Quick Start

  • If a specific ADR is requested (e.g., "Review ADR-0002"), locate docs/decisions/0002-*.md.
  • Read the ADR, locate implementation artifacts, run relevant tests, and assess criteria.
  • Provide a structured report highlighting whether criteria are met and what changed.

Frequently Asked Questions about adr-review

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

FAQPage Schema
How do I review an Architecture Decision Record against its implementation?

ADR review compares your documented architectural decision against the actual codebase. Locate the ADR in docs/decisions/, extract decision outcomes and confirmation criteria, inspect implementation files and tests, then document findings in a structured report showing whether criteria are met.

What should I check when validating an ADR against the codebase?

Validate the decision outcome, confirmation criteria, test expectations, dependencies, timeline, and risks documented in the ADR. Cross-reference these against implementation files and test results to identify deviations, gaps, or changes from the original decision.

Where do I document ADR review findings?

Update the ADR Feedback Log with your findings, gaps, and lessons learned. Generate a structured ADR Review Report that summarizes implementation status, evidence of criteria met or unmet, and any architectural deviations discovered.

Can I review multiple ADRs across different projects?

Yes. The review workflow applies to post-implementation validation across projects. Locate ADRs in each project's docs/decisions/ directory, extract and verify implementation details, then consolidate findings in the ADR Feedback Log.

What happens if the implementation doesn't match the documented ADR decision?

Document the deviation in the ADR Feedback Log with specific evidence from the codebase. The review report highlights gaps between decision and implementation, helping teams understand what changed and why, informing future architectural decisions.

Do I need tests to validate an ADR review?

Tests are part of the validation. Review test expectations documented in the ADR, run relevant tests against the implementation, and compare results to confirmation criteria to assess whether the decision was properly implemented.