What problem does it solve? Documentation chapters and source code drift apart silently when nobody is watching. This Skill runs an unattended, scheduled verification that detects where code has moved ahead of its chapters or where the two conflict, and tracks each divergence as a GitHub issue so a person can act on it. ## Core Features & Use Cases - Scheduled Drift Detection: Invokes devbook:verify-change once per chapter kind across every adopted folder and merges the verdicts into a single report. - Issue Tracking: Opens, updates, or leaves alone GitHub issues labelled devbook-drift, matched by chapter path and heading, so each code-ahead or conflict row has exactly one tracked thread. - Read-Only Reporting: Publishes a merged schedule-report issue including aligned rows, and never writes chapters, briefs, or capture plans itself. - Use Case: A team runs the weekly devbook-verify schedule; the Skill finds a chapter whose code moved ahead, opens a labelled issue naming devbook:capture-specs as the action, and links it in the report. ## Quick Start Run the scheduled devbook verify over every adopted folder and open drift issues for any code-ahead or conflict rows.
