flywheel-operatorlisted

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.
suzworx/flywheel · ★ 4 · Code & Development · score 73

Install: claude install-skill suzworx/flywheel

# Flywheel Operator Flywheel is a durable orchestrator-to-worker loop. **Any agent — or a human — can drive it.** The CLI is the deterministic substrate; the skills are the judgment layer. You are the operator: you decide what runs, who runs it, and whether it landed. The command table below implements [protocol v1](../../docs/PROTOCOL.md). ## What the CLI implements today The table below lists every command `flywheel help` prints, kept in sync with the registry (a doc test fails the build if a command is missing here). Only `flywheel plan`, `retry` and `artifacts` are not built yet; the rest of this skill's manual workflow explains what to do until those three land. | Command | Status | What it does | | --- | --- | --- | | `flywheel init [--track\|--ignore] [--agents-md] [--hooks] [--force]` | **implemented** | Scaffold `flywheel.md` + `.flywheel/state.json` + `.flywheel/events.jsonl` + `.flywheel/briefs/`; `--track` (default) keeps `flywheel.md` a committed file, `--ignore` adds it to the target's root `.gitignore` instead; `--agents-md` writes/refreshes an AGENTS.md block naming the installed skills; `--hooks` writes the Claude/OpenCode session-logging hooks and a Claude Code Stop hook that runs `flywheel gate` (blocks ending the session while work is left unjudged; an existing .claude/settings.json is never overwritten, so add the Stop entry by hand there); refuses an existing state file unless `--force`. Ends with a factory summary: workers, limits, audit policy, enf