feature-workflow-review

To detect feature drift, you inspect active artifacts like SPEC.md, PLAN.md, TASKS.md, and CONTRACT.md against the current diff. This skill identifies discrepancies between your planning documents and implementation, generating a non-blocking drift report for review.

Feature drift is the misalignment that occurs when a feature's active artifacts, such as SPEC.md or PLAN.md, diverge from the actual implementation in the current diff. Detecting this drift surfaces discrepancies early to prevent risky deployments.

No, you cannot use it to block pull requests because it provides non-blocking reporting. It only reports drift between artifacts and the diff without executing quality gates, helping your team decide whether to investigate or adjust artifacts.

You should run a spec review before moving a feature to the next development stage. This confirms alignment between your plan and code, ensuring that artifacts like TASKS.md and CONTRACT.md have not diverged from the current implementation.

No, the skill does not modify your SPEC.md or TASKS.md files. It adheres to a fixed set of outputs to report drift only, enabling your team to manually adjust artifacts or investigate discrepancies without automated file alterations.