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.