flywheel-reality-check

Analyzes gaps between project vision documents and actual implementation, converting findings into tracked beads.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running multi-agent projects accumulate drift between aspirational documentation (AGENTS.md, README.md, plan docs) and what is actually implemented, making it risky to declare a project done without a strategic alignment pass. ## Core Features & Use Cases - Strategic Gap Analysis: Compares vision documents against the real implementation state and surfaces discrepancies. - Gap-to-Bead Conversion: Turns identified gaps into beads tagged reality-check-<YYYY-MM-DD> that an existing swarm can pick up via flywheel_advance_wave. - Depth Selection: Offers three depths via AskUserQuestion — reality check only, reality check plus beads, or a full pipeline launching a fresh 3 cod + 3 cc swarm for gap closure. - Use Case: Before a release, run the reality check to verify that dozens of closed beads actually deliver on the original vision, then auto-generate closure beads for anything missing. ## Quick Start Ask the agent to run a reality check on this project to compare the vision docs against the current implementation and create beads for any gaps found.

Frequently Asked Questions about flywheel-reality-check

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

FAQPage Schema
How do I check if my project implementation matches the original plan?

Run the reality check flow, which reads your vision documents (AGENTS.md, README.md, plan docs) and compares them against the actual implementation state. Identified gaps are converted into beads tagged with the current date for tracking.

What is a gap analysis for multi-agent coding projects?

It is a strategic review pass that verifies the aggregate of closed beads actually delivers on the original project vision. It is typically run before declaring a long-running project done or after drift checks flag significant divergence.

Can I run a reality check during an active flywheel session?

Yes. If a checkpoint exists, the findings produce beads tagged reality-check-<YYYY-MM-DD> that the existing swarm picks up via flywheel_advance_wave. Standalone runs can launch a fresh 3 cod + 3 cc swarm for gap closure.

When should I use reality check instead of drift check?

Use drift check for detecting divergence signals, then reality check for the deeper strategic lens comparing vision docs to implementation. Reality check is the alignment pass before releases or declaring work done.

Does the reality check decide the analysis depth automatically?

No. It presents three labeled options via AskUserQuestion — reality check only, reality check plus beads, or full pipeline — and the user must choose. The skill never picks a depth unilaterally.