using-flywheel

Featured

Operate the Agentic Coding Flywheel through its native workflow. Use when: the caller explicitly selects this factory; convergence and closed work do not prove semantic acceptance.

AI & Automation 446 stars 41 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 97/100

Stars 20%
88
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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...

Details

Author
boshu2
Repository
boshu2/agentops
Created
10 months ago
Last Updated
today
Language
Go
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

flywheel

Drive a durable orchestrator-to-worker implementation loop. Codex or Claude Code act as the orchestrator (plan, brief, dispatch, validate); the OpenCode CLI running the approved DeepSeek worker model does code exploration, implementation, tests, and heavy work. Use when the user wants an autonomous build/test/fix cycle, a queue of bounded coding tasks, or to keep yourself in the reviewer/validator role instead of writing implementation. When the worker is unavailable (missing `opencode` CLI, unauthenticated model, or a provider failure), report the blocker and do not take over implementation yourself.

4 Updated today
suzworx
Code & Development Listed

flywheel-operator

Operate the flywheel framework from any role — human or agent. Use when you want to install flywheel into a repo, validate it is healthy, understand its state, or drive the loop (plan/brief/dispatch/review/correct-or-land) as an operator rather than as a worker. The CLI implements the whole loop except creating and resuming tasks: init, config, log, state, run (through the opencode, claude or sim adapter), validate, inspect, verify, factory, staff, cost, stats, next, status, handoff, trace, claim/release/claims, controller, goal, land and lint. Only `flywheel plan`, `retry` and `artifacts` are still planned — until they land, create and resume tasks with brief files and the raw worker commands shown here.

4 Updated today
suzworx
AI & Automation Listed

flywheel-foreman

Run a line of OpenCode workers. Use when work orders are ready and someone must dispatch them, watch run states, apply the retry policy and pull the andon cord — the mechanical execution side of the loop. You never plan or inspect; you escalate what you cannot classify. Any agent can hold this persona, or the CLI alone (`flywheel supervise`, planned #55).

4 Updated today
suzworx