using-flywheel

# Using the Agentic Coding Flywheel Use the Flywheel only when the caller explicitly selects it. Treat it as a replaceable execution adapter, not a correctness or completion boundary. The adapter cannot select AgentOps semantics, issue a binding verdict, or turn factory completion into delivery or validation proof. Insight: a factory's own completion signals — closed beads, converged agents, a quiet swarm — measure that its machinery finished, not that the result is semantically correct. This skill exists to prevent the failure mode of reporting Flywheel convergence as an AgentOps PASS. ## Choose the factory first AgentOps supports two external software-factory runtimes: Gas City ([using-gc](../using-gc/SKILL.md)) and the [Agentic Coding Flywheel](https://agent-flywheel.com). Use this skill only for the Flywheel. AgentOps supplies skills and evidence contracts to either factory; it does not wrap one factory in the other, and it owns no formulas, roles, or orchestration inside either. ## What the Flywheel is Jeffrey Emanuel's free, open-source stack that turns a dedicated VPS into a supervised multi-agent factory: Claude Code, Codex CLI, and Antigravity CLI as worker runtimes, coordinated through NTM (orchestration), Agent Mail (coordination and file reservations), Beads/BV (task graph), and the wider Flywheel toolset. Its methodology is planning-first: decompose work into beads, run agent swarms against them, and detect convergence between agent outputs. Not for: singl...