Rim · human
1 turn
The outer ring turns once per pass of yours. Slowest ring, and the one that carries the momentum.
2the problem
Why one conversation fails
Design and construction want different speeds.
Most agent workflows collapse design and construction into one conversation. Design is slow and converging, full of open questions; construction is fast, parallel, and wants a settled target. Fused, you design under build pressure or build against a design still moving.
So there are two loops — and one act carries work from the first into the second.
outer loop
Design — an intent
One intent is one tracked change. Its task list is the frontier; the loop's job is burning fog into decisions, writing the destination into the design books, and handing settled slices on.
between them
Your approval
Nothing crosses without it. One approval covers a whole batch, taken on the cheapest channel that can carry it — not a meeting, and not one question per item.
inner loop
Construction — a bolt
One bolt is one construction iteration, tracking a registry of proposals from spec to merged across whatever repositories the work touches. Past your approval it runs without you.
3from idea to merged
One sentence becomes shipped code
Not a straight line — rounds. The intent expands, your word contracts it into construction.
One raw sentence — the kind that arrives in a chat window on a Tuesday — all the way to merged code. But the journey is not a pipeline: an intent breathes. It expands as elaboration rounds open questions, and every round ends the same way — a plan screen, and one word of yours that closes the round, focuses construction, and decides whether anything grows.
“Exports fail when the API rate-limits us.” — one sentence, in motion:
round 1 · the intent expands
retry, queue, or shed load?
what does Retry-After actually promise?
a session works the round → findings, options, evidence
the plan · caps the round
✓ Retry-After promise — answered, with evidenceclosed
✓ retry shape → backoff, capped — a decision recordclosed
⚙ unit · export-backoff · 3 changes→ construction
⊕ next round · harden the export testsexpands
Approveone word · nothing existed on GitHub before it
round 2 · expands again — because you said grow
which failure modes deserve tests?
a shorter session — the intent is narrowing
the plan · caps the round
✓ failure modes — the three worth pinningclosed
⚙ unit · test-hardening · 2 changes→ construction
Approveno new round proposed — the intent is breathing out
nothing left open — the intent is spent, and everything it settled is written down
construction · runs without you
unit · export-backoff
spec · build · merge — your round-1 word covers all of it
unit · test-hardening
arrives from round 2, already approved
merged to main — evidence climbs back out, tasks check themselves off, and the record of every why survives
Each plan is one turn of the wheel. Approving contracts: the round's questions close into records and its settled work drops into construction. Approving a proposed next round is the only way the intent expands. Expansion, contraction, cap after cap — that loop is the flywheel in motion.
Follow a real one, end to end
Pick a sentence. Each page below walks its whole journey a step at a time, with the actual artifact every step leaves.
“Exports fail when the API rate-limits us.”
Code-flavoured — ends in a real diff. Reads best to engineers.
follow this one →
“Onboarding emails arrive out of order.”
A bug whose fix is a design decision, not a patch — the strongest case for the design loop.
follow this one →
“Give the dashboard a dark theme.”
Most legible to a non-engineer — every artifact stays readable.
follow this one →
Intent
1 : 2
One intent agent holds the goal and its units. Both live as OpenSpec, not chat history.
Bolts
1 : 6
Approved units feed a bolt — hours, not sprints. One bolt is one construction iteration, driven by a program.
Construction
1 : 24
Small agents write code and tests against the bolt spec. Fastest ring, shortest memory.
Ratios are the point Inner rings turn faster Spec accumulates at every radius
4your approval
One screen, one word — and how little it costs
The one turn of the wheel nothing else can take for you.
This is the screen the flywheel turns on. A whole round of work — new ideas routed, questions asked, construction proposed — lands in your browser as one plan. Every control already holds the plan's suggestion; you correct what's wrong and approve once. Nothing exists on GitHub until you do.
your browser · the plan, opened for you
Dispatch plan — Tuesday's ideas, routed
Controls hold the plan's suggestion. Change any, then approve once — nothing exists on GitHub until you do.
intent · export-backoff — new
Exports fail when the API rate-limits usits first questions
researchWhat does the API's Retry-After actually promise? — read the client, probe the live behaviour, answer with evidence.
approvequestionRetry, queue, or shed load? — or type the answer here and it closes now.
answeredbolt · site-refresh — open, folds in
site-refreshdeliverable: the new pages, live
unitoverview-page — 1 change · the reference page, linked from the topbar.
bolt-planunitconcept-tours — 3 changes · one journey page per idea.
backlog
Approve
…or say what's wrong and
Send back
The real surface, drawn to scale: containers for each intent and bolt, one row per outcome, a route control on every row. Over Discord the same plan is a numbered digest and “yes to all” is the same approval.
what you do
Correct, don't compose
Every choice arrives already made. You change a route, rename a bolt, type an answer — or touch nothing.
what it costs
One approval, one round
Not one question per item, and not a meeting to arrive at it. The whole routed round crosses in a single act.
what follows
Then it runs without you
The approved work is filed, the loops pick it up, and it comes back only as evidence — or a question only you can answer.
It comes back to you when there is something to show, or a question only you can answer. Your attention is the scarce ring, and everything else is built to turn faster around it.
5install
Two commands
The repository is its own marketplace.
/plugin marketplace add agentplot/flywheel
/plugin install flywheel@flywheelWhere the rest of it is written down
- The README — the whole machinery in prose.
- skills/ — the two loop skills and the thirteen session-type skills.
- agents/ — the agent profiles, one file each.
- schemas/ — the OpenSpec workflow schemas, published as user schemas.