Dev10x:playbook-maintenance

To detect drift in playbook overrides, you can run a scan that locates all user override files and matches them to default playbooks by filename, comparing each override to identify new steps, prompt changes, and fragment drift.

Playbook drift occurs when user override files are not updated to match changes made to the default playbooks over time, leading to intentional or unintentional divergences in workflow steps and prompt configurations.

To fix prompt changes and fragment drift, the maintenance process generates structured findings from its drift analysis and then delegates the actual edits to the Dev10x:playbook skill for applying changes.

Yes, you can automatically scan for new or removed steps by running the playbook maintenance command, which compares your override files against the default playbooks and produces a structured report of all differences.

No external dependencies are required to run the playbook drift detection process, as it operates by independently locating override files, matching them to defaults by filename, and analyzing the differences internally.