Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →avizmarlon/agent-flywheel
Use when planning a new project or feature, turning an idea or specification into an executable plan, designing architecture, establishing a roadmap or phase, or coordinating multi-session or multi-agent builds. Activate on "plan this build", "turn this into tasks", "make it a plan", or when tasking/swarm coordination is mentioned. Skip routine bugfixes, urgent ops/incidents, or executing pre-approved plans unless re-planning is requested.
Passed 22 of 22 test cases with the skill, and 13 of 22 without it.
and 12 more in the full report
9 fixed13 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our project has 15 interconnected tasks spanning multiple sessions. We want to use Mode B for execution. What specific file format should be used for the task graph?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies JSONL as the format for the structured task graph | Missed | Passed |
The instructions your model reads when the skill loads.
A reusable, systematic method for planning and executing software projects with AI agents. Core principle: invest heavily in plan-space before code — that's where errors are cheapest to fix. Inspired by Jeffrey Emanuel's Agent Flywheel framework (agent-flywheel.com).
The "flywheel" metaphor: each iteration upgrades plan quality, artifact reusability, and execution speed. Rework caught in planning costs ~1× effort; in task definition ~5×; in code ~25×. This heuristic shapes where to push reasoning (upstream, to the plan).
Use this skill when:
Do NOT use when:
Don't default to heavy machinery. Choose the lightest mode that fits the scope.
| Mode | When to use | Substrate | Complexity |
|---|---|---|---|
| A: Plan-only | Small/sequential projects; solo or tight-knit teams; coherent slice | Markdown plan + test-driven development + standard PR workflow | Minimal |
| B: Plan + task graph | Multiple interconnected tasks; multi-session risk; dependency chains | Markdown plan + structured task graph (JSONL format) + single-agent execution | Medium |
| C: Task-graph + routable beads | Plan B + need resumability across context loss; durable task store | Structured beads + dependency routing + PR-per-cluster | Medium–High |
| D: Full multi-agent swarm | Large, highly parallel work; amortized coordination cost | Only after passing swarm-readiness.md — full coordination layer | High |
Default to Mode A. Escalate only when conditions in beads-escalation.md are genuinely met. Most projects do not justify modes B–D.
test cases passed, vs 13 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.