Menu
Targeted scan of specific paths or concerns without a full flywheel scan.
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-scan |
| description | Targeted scan of specific paths or concerns without a full flywheel scan. |
Targeted repository scan. $ARGUMENTS (optional: path or focus area)
Ask the user what to focus on (if not specified in $ARGUMENTS):
Use Agent(Explore) with the specified focus to perform a targeted scan.
Call flywheel_profile via the agent-flywheel MCP server with cwd and optional goal = the focus area.
Display the scan results:
Ask: "Would you like to start a flywheel cycle targeting these findings?"
