skills.rest
joestump
joestumpCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

check

Detect drift between code and governing ADRs and specs.

30|2|Updated Feb 13, 2026
Search Tags:#architecture#adr#compliance#spec#drift-detection#code-analysis#findings
One-click install
npx skills add https://github.com/joestump/claude-plugin-design --skill check-joestump
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/joestump/claude-plugin-design/tree/main/skills/check
Command: npx skills add https://github.com/joestump/claude-plugin-design --skill check-joestump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a fast, focused way to detect drift between implementation and its governing architecture artifacts so teams can quickly find and address mismatches without running a full audit.

Core Features & Use Cases

  • Targeted Drift Detection: Analyze a specific file, directory, ADR reference, or SPEC reference to determine alignment with ADRs and specs.
  • Three-category Analysis: Produce findings for Code vs. Spec, Code vs. ADR, and ADR vs. Spec with prioritized severities.
  • Actionable Findings: Output a structured findings table with severity, source artifact identifiers, and file paths with line numbers to facilitate rapid remediation.
  • Use Case: Run a quick check on a changed module before merging to ensure no MUST/SHALL requirements are violated and to catch terminology or approach mismatches early.

Quick Start

Run a drift check on src/auth/login.ts to compare implementation against ADRs and specs and produce a findings table.

Frequently Asked Questions about check

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

FAQPage Schema
How do I detect code drift from architecture decision records and specs?▼

To detect code drift from ADRs and specs, run a targeted check against a specific file, directory, or ADR/SPEC reference. The analysis compares implementation against governing artifacts to quickly identify mismatches in approach and terminology.

What is the difference between MUST, SHALL, and SHOULD violations when checking spec coverage?▼

When checking spec coverage, MUST and SHALL requirements are verified as critical violations, while SHOULD requirements are treated as warnings. This severity prioritization helps teams focus on the most impactful architectural mismatches first.

Can I check ADR adherence for a single file instead of running a full audit?▼

Yes, you can check ADR adherence for a single file or directory instead of running a full audit. This targeted drift detection allows you to analyze a specific module, such as a changed file before merging, to quickly ensure compliance.

How do I find mismatches between ADRs and specs before merging a changed module?▼

To find mismatches between ADRs and specs before merging, run a quick drift check on the changed module. The analysis produces a structured findings table covering Code vs. Spec, Code vs. ADR, and ADR vs. Spec categories to catch violations early.

What output format does drift detection produce for code and architecture mismatches?▼

Drift detection produces an actionable findings table for code and architecture mismatches. The output includes severity levels, source artifact identifiers, and file paths with line numbers to facilitate rapid remediation of the identified violations.

Related Skills

Explore More Software Engineering Skills→
scomofoscomofo

dev-story

Implement sprint stories into production code with required automated tests.

Community
Advanced
CANTAGESTUDIOCANTAGESTUDIO
3

refactor-arch-hotspots

Detect architectural hotspots by analyzing churn, coupling, and layer violations.

Community
Advanced
specd-sddspecd-sdd
12

specs-compliance

Audit specs against code implementations to detect drift and verify test coverage.

Official
Advanced
solitasrohsolitasroh
2

code-review

Analyze code quality and detect bugs across files, directories, or PRs.

Community
Advanced