flywheel-status

Displays flywheel checkpoint state, bead progress, inbox messages, and next recommended bead.

3|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-status-burningportra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flywheel-status
Source: https://github.com/burningportra/agent-flywheel-plugin/tree/main/skills/flywheel-status
Command: npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-status-burningportra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running a multi-phase agent flywheel workflow, it is hard to know where the project stands: which phase is active, how many beads are done, whether agents have sent messages, and what to work on next. This Skill consolidates all of that into a single status report. ## Core Features & Use Cases - Checkpoint Summary: Reads .pi-flywheel/checkpoint.json to show the current phase, selected goal, bead completion counts, elapsed phase time, and polish convergence score. - Live Bead Table: Runs br list --json to display beads grouped by status (in_progress, open, closed/deferred) with priority and review passes. - Inbox & Next Steps: Fetches and acknowledges Orchestrator messages via the agent-mail MCP tool, shows the current todo list, and runs bv --robot-next to recommend the next optimal bead. - Use Case: After resuming a session, ask for flywheel status to instantly see that you are in the implement phase with 4 of 9 beads closed, one agent message pending, and which bead to pick up next. ## Quick Start Ask the assistant to show the current flywheel status for this project.

Frequently Asked Questions about flywheel-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check flywheel status and bead progress?▼

Invoke the flywheel-status skill, which reads .pi-flywheel/checkpoint.json for the current phase and goal, then runs br list --json to show a bead table grouped by status with priority and review passes.

How do I find the next bead to work on in agent-flywheel?▼

The status report runs bv --robot-next via Bash, which returns the next optimal bead based on the dependency graph. It appears as the final section of the flywheel status output.

Does flywheel-status show messages from running agents?▼

Yes. It calls fetch_inbox via the agent-mail MCP tool with agent_name Orchestrator, displays messages from running agents, and acknowledges each read message with acknowledge_message.

What happens if the checkpoint file is missing?▼

The skill expects .pi-flywheel/checkpoint.json to exist from a prior flywheel run. If it is absent, the checkpoint section cannot be displayed, so run flywheel setup or start a flywheel session first.

Can I see how long the current phase has been running?▼

Yes. The status report computes elapsed time in the current phase from the phaseStartedAt field in checkpoint.json, and also shows the polish convergence score when in the planning phase.