drift-detection

Detect and log specification-implementation drift across development phases.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/I2olanD/dotfiles --skill drift-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift-detection
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/drift-detection
Command: npx skills add https://github.com/I2olanD/dotfiles --skill drift-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drift between specifications and implementation during development is detected and tracked to prevent unrecorded scope changes, missing requirements, contradictions, or unnecessary work. This skill provides a structured approach to identify, categorize, and log drift so the spec README remains a trustworthy source of truth.

Core Features & Use Cases

  • Drift Typing: Classifies drift into Scope Creep, Missing, Contradicts, and Extra based on spec vs implementation.
  • Phase Analysis: Analyzes modified files, annotations, tests, and specification context to surface drift during active development.
  • Logging & Reporting: Generates drift reports and appends entries to the spec README for auditability.
  • Integration: Works with constitution-validation and spec-management workflows to maintain alignment across phases.

Quick Start

Run drift-detection during a development phase to compare the current codebase against the active PRD/SDD/PLAN, review drift findings, and update the spec README's Drift Log accordingly. Example commands:

  • Activate drift detection for the current phase and generate a drift report.
  • Review drift findings and add appropriate drift log entries to the spec README.

Frequently Asked Questions about drift-detection

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

FAQPage Schema
How do I detect spec drift between my implementation and specifications?

Spec drift is detected by analyzing modified files, tests, and spec context to surface scope creep, missing features, contradictions, or extra work. Comparing the current codebase against active PRD, SDD, or PLAN documents identifies where implementation diverges from specifications.

What is the best way to track scope creep and missing requirements during development?

Tracking scope creep involves classifying drift into Scope Creep, Missing, Contradicts, and Extra categories, then generating a structured drift report. Appending these entries to the spec README ensures unrecorded scope changes and missing requirements remain auditable.

How do I log spec implementation divergence in my documentation?

Logging spec implementation divergence requires generating a structured drift report and appending entries to the spec README Drift Log. This updates documentation to ensure the spec remains a trustworthy source of truth for unrecorded changes.

Can I use drift detection across different development phases?

Drift detection applies across development phases by analyzing modified files, annotations, tests, and spec context. It surfaces phase-specific scope creep, contradictions, or missing features by evaluating implementation changes against active PRD, SDD, or PLAN documents.

Does drift detection work with spec management and constitution validation workflows?

Drift detection integrates with constitution-validation and spec-management workflows to maintain alignment across development phases. It generates structured drift reports and log entries that synchronize spec README documentation with active development changes.