flywheel

Source contract preview

This generated excerpt gives readers the beginning of the live primitive contract before they jump to GitHub.

Compose cycles of: pick a backlog item → `/shape` (if unshaped) →
`/implement` → `/yeet` → `/deliver --polish-only` → `/ship` → `/monitor` →
loop.

Abbreviated form using the convenience composer:
pick → `/deliver` → `/yeet` → `/ship` → `/monitor` → loop.
(`/deliver` = `/shape` → `/implement` → clean loop; `/deliver --polish-only`
runs that same clean loop on an existing branch.)

> Migration: the polish step was `/settle` until backlog 080 collapsed it into
> `/deliver --polish-only`; `/settle` is a deprecated redirect for one release.

You already know how to do each of these. This skill exists only to
encode the invariants that aren't inferable from the leaf names.

## Invariants

- Flywheel composes. Phase logic lives in the leaf skill. Flywheel has none.
- State lives in leaf receipts, git, and `backlog.d/`. Flywheel has none.
- If `.harness-kit/flywheel.yaml` exists, load it once at cycle start with the
  Harness Kit config loader and use it only for cycle tuning: cadence,
  `max_cycles`, token budget, backlog include filters, and stop conditions.
  If absent, use invocation flags and built-in defaults.
- Provider-roster behavior lives in the leaf workflow skills. If the repo has
  `.harness-kit/agents.yaml`, `/flywheel` expects two or more roster-member
  receipts or explicit exceptions in phase evidence, but it does not dispatch
  providers directly.
- The cycle closeout includes the roster delegation report from `/ship`,
  plus any provider-health follow-ups surfaced by failed or low-signal lanes.
- `/ship` owns closure: squash-merge, backlog archive, `/reflect`, and
  applying reflect's outputs. Flywheel does not invoke `/reflect` directly.
- Ship before deploy. Always.
- Harness edits from reflect never touch master. `/ship` routes them to
  `harness/reflect-outputs` for human review.
...