flywheel

Orchestrate backlog item cycles across deliver, settle, deploy, monitor, and reflect.

2|Updated Oct 2, 2025

Search Tags:#automation #workflow #devops #orchestration #backlog #cycle #flywheel

Ready to run

npx skills add https://github.com/misty-step/volume --skill flywheel-misty-step

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flywheel
Source: https://github.com/misty-step/volume/tree/main/.agents/skills/flywheel
Command: npx skills add https://github.com/misty-step/volume --skill flywheel-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Outer-loop shipping orchestrator that composes the sequence of leaf steps (deliver, land, deploy, monitor, and reflect) per backlog item and applies reflect outputs back to the harness and backlog before looping.

Core Features & Use Cases

Orchestrates end-to-end cycles across backlog items from intake to reflection.
Maintains invariants about state in receipts, git, and backlog, while keeping memory in sync.
Enforces deployment gating and cycle hygiene (e.g., pre-deploy checks, review gates) before shipping.

Quick Start

Run a flywheel cycle on the current backlog to process the next items.

Frequently Asked Questions about flywheel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I orchestrate end-to-end backlog cycles from delivery to reflection?▼

Backlog cycles are orchestrated by sequencing deliver, settle, deploy, monitor, and reflect steps, then applying reflect outputs back to the backlog before looping. This enforces governance gates and maintains state invariants across artifacts.

What is the best way to automate DevOps workflow sequencing for iterative backlog items?▼

Automating DevOps workflow sequencing requires an outer-loop orchestrator that coordinates leaf skills across iterative backlog items. It schedules cycles, enforces deployment gating, and ensures proper approvals and artifacts are generated before shipping.

Can I enforce deployment gating and review gates during backlog cycle orchestration?▼

Deployment gating and review gates are enforced during backlog cycle orchestration to ensure cycle hygiene. Pre-deploy checks and governance gates verify proper sequencing, approvals, and artifacts before allowing deployment and cycle closure.

How does backlog cycle orchestration maintain state across git, receipts, and the backlog?▼

Backlog cycle orchestration maintains state invariants by keeping memory in sync across git, receipts, and the backlog. The orchestrator coordinates leaf steps and ensures state consistency throughout the delivery, settling, and deployment phases.

When do I need an outer-loop orchestrator for backlog item processing?▼

An outer-loop orchestrator is needed when processing iterative backlog items requires strict sequencing of deliver, land, deploy, monitor, and reflect phases. It composes leaf steps, applies reflect outputs to the harness, and enforces governance gates.

Does flywheel require specific dependencies to coordinate end-to-end backlog cycles?▼

Flywheel coordinates end-to-end backlog cycles without external dependencies, relying on leaf skills for execution. It maintains state in receipts and backlog while applying reflect outputs back to the harness before looping.