skills.rest
burningportra
burningportraCOMMUNITY
Explore all skills by this author →
GitHub

flywheel-stop

Stops the active flywheel session and clears checkpoint state.

3|1|Updated Apr 15, 2026
Search Tags:#multi-agent#mcp#orchestration#checkpoint#flywheel#task cleanup#session teardown
One-click install
npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-stop-burningportra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flywheel-stop
Source: https://github.com/burningportra/agent-flywheel-plugin/tree/main/skills/flywheel-stop
Command: npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-stop-burningportra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a multi-agent coding flywheel session needs to be halted, leftover checkpoints, bead locks, file reservations, and orphaned tasks can block a clean restart. This Skill tears down the active session safely so you can start fresh without stale state. ## Core Features & Use Cases - Session State Inspection: Reads .pi-flywheel/checkpoint.json to show the current phase, goal, and bead progress before stopping. - Confirmed Teardown: Asks for user confirmation, then releases bead locks via the agent-flywheel MCP server, deletes the checkpoint file, and releases file reservations through the agent-mail MCP tool. - Task Cleanup: Finds active flywheel tasks with TaskList and marks each as deleted so nothing keeps running in the background. - Use Case: You started a flywheel run against the wrong branch. Run this Skill to release all bead locks and file reservations, clear the checkpoint, and then relaunch with /agent-flywheel:start. ## Quick Start Stop the current flywheel session, release all bead locks and file reservations, and clear the checkpoint state.

Frequently Asked Questions about flywheel-stop

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

FAQPage Schema
How do I stop a running agent-flywheel session?▼

Invoke the flywheel-stop skill, which reads the checkpoint file, asks for confirmation, releases bead locks and file reservations, deletes .pi-flywheel/checkpoint.json, and cancels active tasks. You can then restart with /agent-flywheel:start.

How to release file reservations in a multi-agent Claude Code workflow?▼

The stop procedure calls release_file_reservations through the agent-mail MCP tool with project_key set to the current working directory. This frees files reserved by agents so other sessions can modify them.

What happens if there is no active flywheel session?▼

The skill checks .pi-flywheel/checkpoint.json first. If no active session exists, it reports "No active session found" and takes no further action, so it is safe to run idempotently.

Does stopping the flywheel delete my code changes?▼

No. The stop procedure only clears orchestration state: the checkpoint file, bead locks, file reservations, and tracked tasks. Your source files and any committed work remain untouched.

Why are bead locks still held after stopping a session?▼

Bead locks persist if the stop flow is interrupted before calling flywheel_approve_beads with action reject. Re-run the stop skill to release locks through the agent-flywheel MCP server and clear remaining state.

Related Skills

Explore More Software Engineering Skills→
eaasxteaasxt

prime

Bootstrap a new agent workflow through four coordinated startup phases.

Community
Advanced
ManuelKugelmannManuelKugelmann
3

claude-restart

Restart Claude Code sessions to reload skills or manage context.

Community
Intermediate
ruvnetruvnet
70.1k

ruflo-status

Diagnose Ruflo health and report system, MCP server, and active-agent status.

Community
Basic
AO-Cyber-SystemsAO-Cyber-Systems

df:pause-work

Generate a .continue-here.md handoff file with timestamp and WIP commit.

Official
Intermediate