Menu
Check if the codebase has drifted from the implementation plan.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Full health check of the codebase and flywheel dependencies.
Deep research on an external GitHub repository to extract implementation insights.
Set up flywheel prerequisites for this project.
Start or resume the full agentic coding flywheel. Drives the complete workflow: scan → discover → plan → implement → review.
Stop the current flywheel session and reset state.
Launch a parallel swarm of agents to implement multiple beads simultaneously.
| name | flywheel-drift-check |
| description | Check if the codebase has drifted from the implementation plan. |
Run a strategic drift check. $ARGUMENTS
Read the plan document path from .pi-flywheel/checkpoint.json (planDocument field). If not found, scan docs/plans/ for the most recent plan file.
Read the current bead statuses: br list --json via Bash.
Run bv --json via Bash for graph analysis (cycles, orphans, bottlenecks).
Use Agent(Explore) to compare current code state against the plan:
Display a drift report:
✅ On track: N beads
⚠️ Potentially stale: N beads
❌ Blocked: N beads (dependency issues)
🔄 New opportunities: (not in original plan)
Ask: "Would you like to update the plan to address the drift? (This will trigger a polish loop)"
If yes, call flywheel_approve_beads with action: "polish" via the agent-flywheel MCP server.