What problem does it solve? Multi-agent coding workflows depend on a chain of external tools (bead tracker, bead visualizer, agent-mail server, MCP server) and on-disk state that can silently drift or break. Without a periodic audit, developers discover broken dependencies, orphaned beads, or accumulating technical debt only when the workflow stalls mid-task. ## Core Features & Use Cases - Dependency verification: Checks versions of br and bv, pings the agent-mail liveness endpoint, inspects git status, checkpoint state, and MCP server build output in parallel. - Codebase health scan: Counts TODO/FIXME/HACK markers, computes test-to-source file ratios, and surfaces lint or compilation issues via an Explore agent. - Bead graph audit: Runs br list and bv to count open/closed/in-progress/deferred beads and detect cycles or orphaned beads, then renders a formatted report with a health score out of 10. - Use Case: Run it on a weekly cadence to confirm the agent-flywheel toolchain is healthy before starting a large multi-agent implementation wave. ## Quick Start Ask the agent to run a full flywheel health check and report the health score for dependencies, codebase, and beads.