implementation-drift-check

Implementation drift detection compares current code against specs or plans to find deviations. This skill uses git and filesystem access to retrieve artifacts, analyzing them with Python to report alignment issues during code review or shipping phases.

Specification compliance checks are needed during code review and shipping phases to catch drift proactively. You can also explicitly invoke drift detection during implementation stages to verify that your code aligns with OpenSpec changes or live intent documents.

You can verify code alignment by running a drift detection skill that retrieves artifacts via git and filesystem access. It analyzes your implementation against specifications or plans using Python, identifying and reporting deviations for code review.

Yes, you need Python and git to run implementation drift detection. The skill requires git and filesystem access for artifact retrieval and diffing, while Python is utilized for the actual analysis and reporting of specification deviations.

Yes, you can use this drift detection skill with legacy specifications. It performs multi-source analysis, considering various inputs like OpenSpec changes, live intent documents, and legacy specifications to identify deviations in your implementation.

The best way to automate drift checks during shipping is to run a specification compliance skill that compares implementation against plans. This proactively catches drift using Python analysis and git artifact retrieval during code review and shipping phases.