using-flywheel

name	using-flywheel
description	Operate the Agentic Coding Flywheel as a caller-selected software factory; keep its runtime state out of AgentOps verdicts. Triggers: "using flywheel", "agent flywheel".
practices	["team-topologies","design-by-contract"]
skill_api_version	1
hexagonal_role	driving-adapter
consumes	["explicit-packets"]
produces	["flywheel-runtime-evidence"]
context_rel	[{"kind":"partnership","with":"using-gc"}]
user-invocable	true
metadata	{"tier":"execution","dependencies":[],"capabilities":["route_to_native_flywheel_workflow","expose_agentops_skills","observe_flywheel_runtime"],"effects":[],"canonical_status":"canonical","disposition":"keep_optional_adapter","stability":"experimental"}

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) and the Agentic Coding Flywheel. 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: single-session local work (use the default one-agent loop), Gas City cities (use using-gc), or as a verdict source.

Inputs

• An explicit caller selection of the Flywheel as the factory.
• A provisioned Flywheel host, or authorization to provision one via the upstream wizard.
• The caller-owned work intent (beads or a decomposable goal).

Procedure

1. Provision with the upstream wizard at agent-flywheel.com (OS selection through final verification; a single-curl install on a dedicated Ubuntu VPS), then run its onboard tutorial once. AgentOps does not fork, pin, or mirror the Flywheel stack; upstream owns its installer and versions.

2. Make AgentOps skills visible to each worker runtime the Flywheel drives (Claude Code, Codex CLI, Antigravity CLI), using the install paths in the repository README. Verify per runtime:

   ls ~/.claude/skills/validate ~/.codex/skills/validate 2>/dev/null
   

   A runtime that cannot list the skill will never invoke it.

3. Run the Flywheel's native workflow — bead decomposition, swarm dispatch, convergence — unchanged. Skill presence and skill invocation are different facts: when an AgentOps skill's use is an acceptance condition, name it on the work item or worker prompt, and check the transcript for its use.