Menu
Show current flywheel status, bead progress, and inbox messages.
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
| name | flywheel-status |
| description | Show current flywheel status, bead progress, and inbox messages. |
Show flywheel status for this project.
Checkpoint: Read .pi-flywheel/checkpoint.json. Display:
phaseStartedAt)Live beads: Run br list --json via Bash. Display a table:
ID | Title | Status | Priority | Review passes
Group by: in_progress → open → closed/deferred.
Inbox: Call fetch_inbox via the agent-mail MCP tool with agent_name: "Orchestrator". Display any messages from running agents. Acknowledge read messages by calling acknowledge_message for each.
Todos: Display current todo list from TodoRead.
Next recommended bead: Run bv --robot-next via Bash to get the next optimal bead to work on.
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.