All authors
Claude Skills by suzworx
github.com/suzworx9 skills0 installs8 views
- Flywheel AuditorIndependently audit flywheel's records. Use when a first article is due, a sample of the line is being checked, or the traveler looks incomplete: re-measure in a clean environment, re-inspect, check the traveler is complete and consistent, check whether QC caught what it should have, and file nonconformances. You never work the line and never discuss a unit with the line before reporting. Prefer a different model or vendor than the line.Votes: 0GitHub stars: 4
- Flywheel ForemanRun 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).Votes: 0GitHub stars: 4
- Flywheel InspectorQC-inspect finished flywheel units. Use when a work order has run and reported done: verify the unit against its work order using gauge readings for the same git tree, apply the review traps, and give a verdict — pass, rework (with a delta), scrap, or escalate. You never run the gauges as evidence, never fix, and never inspect your own session's work. Any agent can hold this persona.Votes: 0GitHub stars: 4
- Flywheel OperatorOperate 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, c...Votes: 0GitHub stars: 4
- Flywheel PlannerPlan flywheel work orders. Use when a spec or goal must become bounded, single-purpose tasks with `owns:`/`needs:`/`exclusive:`, gates and acceptance criteria — before any dispatch. You write the work orders; you never dispatch them. Any agent can hold this persona; the worker stays OpenCode.Votes: 0GitHub stars: 4
- Flywheel StewardTurn flywheel signals and nonconformances into learnings. Use when signals are untriaged, nonconformances have been filed, or a session is about to end: triage each into a learning (Observed / Evidence / Ask) with a corrective action, deduplicate against known issues, and prepare upstream feedback only with the user's consent. You never change units. Any agent can hold this persona.Votes: 0GitHub stars: 4
- Flywheel WorkerThe worker side of the flywheel loop. Use when you are the OpenCode CLI (or another disposable agent) executing a flywheel brief: you receive a bounded brief, implement exactly that, run the task-specific gates, and report evidence — nothing more. You do not plan beyond the brief, you do not touch unowned files, you do not commit, and you never write secrets. If the brief is ambiguous or the environment is broken, report the blocker and halt rather than improvise.Votes: 0GitHub stars: 4
- FlywheelDrive a durable orchestrator-to-worker implementation loop. Codex or Claude Code act as the orchestrator (plan, brief, dispatch, validate); the worker configured in .flywheel/config.json (a claude, codex or opencode adapter running the approved 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...Votes: 0GitHub stars: 4
- Flywheel ReviewerReview a finished flywheel unit's diff as an independent agent. Use when `flywheel review <task> --agent` hands you a unit: read the brief and every correction delta after it (in order, a later one overriding an earlier one), the gate readings, the diff from the dispatch base and the files around it, and report concrete defects as findings with a failure scenario, a file, a real line and a fix hint. You never edit, never run git writes, never review your own work and never pass a unit. Prefer...Votes: 0GitHub stars: 4