菜单
Operate the Agentic Coding Flywheel as a caller-selected software factory; keep its runtime state out of AgentOps verdicts. Triggers: "using flywheel", "agent flywheel".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/boshu2/agentops --skill using-flywheel命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use Agent Mail as an optional messaging and file-reservation adapter for explicitly coordinated writers. Triggers: "coordinate writers", "reserve files".
Operate explicit orchestrator, implementer, validator, and scribe roles through a caller-selected agent runtime. Triggers: "agent-native factory", "role-shaped agent panes", "persistent workers".
Initialize minimal AgentOps documentation and verdict storage without taking over repository workflow. Triggers: "bootstrap AgentOps", "initialize AgentOps docs".
正在显示 SKILL.md
| 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"} |
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.
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.
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.
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.
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.
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.
Read Flywheel runtime state (bead graph, Agent Mail threads, NTM pane truth) as evidence pointers only. When agents disagree with tracker state, trust the more direct observation: pane truth over roster claims, bead state over prose.
Two consecutive non-converging swarm rounds on the same intent is the stop condition: stop, report the divergence to the caller, and do not dispatch a third round on your own authority.
Runtime evidence pointers for the caller: which beads the Flywheel processed,
where the candidate commits and worktrees live, and which AgentOps skills its
agents actually invoked. Done when the caller holds those pointers and — if
proof was requested — a fresh validate context has judged the exact
candidate. Factory state alone is never the done signal.
Report the concrete failure — unreachable host, missing skill visibility, non-convergence, or an upstream installer change — and stop. Upstream Flywheel defects belong to its maintainer; the caller owns any revision, retry, or factory switch.