with one click
flywheel-rollback
Roll back a completed bead implementation.
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.
Menu
Roll back a completed bead implementation.
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
Relentless goal/design interview that sharpens framing and writes durable docs (brainstorm artifact, ADRs, glossary) as decisions crystallize. Use when refining a flywheel goal, pressure-testing scope, or "grill with docs".
Start or resume the full agentic coding flywheel. Drives the complete workflow: scan → discover → plan → implement → review.
Set up flywheel prerequisites for this project.
One-shot diagnostic of every flywheel dependency — MCP connectivity, Agent Mail liveness, br/bv/ntm/cm binaries, node version, git status, dist-drift, orphaned worktrees, and checkpoint validity. Use when debugging toolchain issues, before starting a new session, after /flywheel-cleanup, or as a CI gate.
Strategic gap analysis between vision (AGENTS.md / README.md / plan docs) and what's actually implemented. Converts gaps into beads, optionally launches a swarm. Use when "reality check", "where are we really", "gap analysis", "did we drift", or before declaring a long-running project done.
Launch a parallel swarm of agents to implement multiple beads simultaneously.
| name | flywheel-rollback |
| description | Roll back a completed bead implementation. |
Roll back a bead implementation. $ARGUMENTS (optional: bead ID)
If a bead ID is provided in $ARGUMENTS, use it. Otherwise, run br list --json and show completed beads for the user to choose from.
Show the commits associated with the selected bead: git log --oneline -10 via Bash.
Ask: "Which commit marks the start of bead <id>? (Or: roll back to before this bead was implemented)"
Ask the user to confirm: "This will revert changes. Are you sure?"
If confirmed:
git revert <commit> or git revert <from>..<to> via Bash (prefer revert over reset).br update <id> --status open via Bash.beadResults.TaskList to find the task for this bead, then TaskUpdate(taskId: "<id>", status: "deleted") to cancel it.Confirm: "Rolled back bead <id>. It is now open and ready to re-implement."