ADR & Drift Review

Review ADRs for conflicts, broken supersede chains, and spec drift.

Updated Aug 27, 2026

Search Tags:#architecture #code review #drift detection #adr #consistency check #spec alignment

Ready to run

npx skills add https://github.com/rghsoftware/context-engine --skill adr-drift-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ADR & Drift Review
Source: https://github.com/rghsoftware/context-engine/tree/main/context-engine/skills/adr-review
Command: npx skills add https://github.com/rghsoftware/context-engine --skill adr-drift-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the review of architectural decisions (ADRs) and checks for inconsistencies or deviations (drift) between documented decisions and the current state of the project's specifications and features.

Core Features & Use Cases

ADR Consistency Check: Validates ADRs for conflicts, broken supersede chains, and references to non-existent files.
Spec Drift Detection: Compares active feature specifications against ADRs to identify contradictions or outdated assertions.
Coverage Gaps: Highlights areas where changes lack corresponding ADRs or planning artifacts.
Use Case: Before merging a significant feature, use this Skill to ensure all architectural decisions are consistent and that the implemented code aligns with the documented specifications, preventing technical debt and architectural decay.

Quick Start

Run a comprehensive project-level review of architectural decisions and spec alignment.

Frequently Asked Questions about ADR & Drift Review

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

FAQPage Schema

How do I check for architectural drift between my feature specs and documented decisions?▼

To check for architectural drift, compare active feature specifications against ADRs to identify contradictions, outdated assertions, and coverage gaps where code changes lack corresponding planning artifacts.

What is an ADR consistency check and when do I need it?▼

An ADR consistency check validates architectural decision records for internal conflicts, broken supersede chains, and invalid file references. You need it before merging significant features to prevent architectural decay and technical debt.

How do I find coverage gaps where code changes lack planning artifacts?▼

To find coverage gaps, perform a project-level review that cross-references active features against ADRs, highlighting areas where implementation changes exist without corresponding architectural decision records.

Can I detect broken supersede chains in my architecture decision records automatically?▼

Yes, automated ADR review analyzes your architecture decision records to detect broken supersede chains, conflicts between records, and references to non-existent files across the project.

What's the best way to ensure spec alignment before merging a major feature?▼

The best way to ensure spec alignment is running a comprehensive review combining ADR consistency checking with drift detection to verify implemented code matches documented specifications.

Why does my project have architectural inconsistencies despite documented decisions?▼

Architectural inconsistencies occur when feature specifications drift from ADRs over time. Automated drift detection identifies contradictions, outdated assertions, and missing planning artifacts causing these inconsistencies.