What problem does it solve? Long-running coding projects drift: the plan written at kickoff no longer matches what the code actually does, beads go stale, and new requirements appear that the plan never covered. This Skill compares the current codebase against the saved plan and bead graph so you can catch divergence before it derails implementation. ## Core Features & Use Cases - Plan-vs-code comparison: Reads the plan document from .pi-flywheel/checkpoint.json (or the latest file in docs/plans/) and uses an Explore agent to check which planned changes are implemented, stale, or missing. - Bead graph analysis: Runs br list --json and bv --json to surface blocked beads, dependency cycles, orphans, and bottlenecks. - Drift report with routing: Displays on-track, stale, blocked, and new-opportunity counts, then asks via AskUserQuestion whether to polish the bead graph, run a full reality-check, or ignore the drift. - Use Case: After a week of implementation, run a drift check to discover that 4 beads are stale and 2 new requirements emerged, then polish the bead graph in place instead of replanning from scratch. ## Quick Start Ask the agent to run a drift check comparing the current codebase against the saved implementation plan and bead statuses.
