Pepcode Cancel Skill FAQs

Question 1

How does the skill handle unresponsive team members?

Accepted Answer

The skill uses a two-pass protocol. If a member doesn't respond to a shutdown request within 15 seconds, it enters a reconciliation pass and eventually uses a best-effort cleanup to ensure the team is dismantled.

Question 2

Is the cancel skill session-specific?

Accepted Answer

Yes, it follows a session-aware state contract, meaning it can target specific session paths without interfering with other active Claude Code sessions.

Question 3

What order are modes cancelled in?

Accepted Answer

Modes are cancelled in dependency order, starting from high-level orchestrators like Autopilot and Ralph, down to standalone modes like Ultrawork, Swarm, and finally native Team configurations.

Question 4

Can I use this to reset my entire Pepcode environment?

Accepted Answer

Yes, running the command with the --force flag will enumerate all sessions and legacy artifacts, removing them to provide a completely clean state.

Question 5

Does using the cancel skill delete my work progress?

Accepted Answer

By default, the cancel skill preserves progress for modes like Autopilot to allow for later resumption. Only the --force or --all flags will completely erase session artifacts.

Pepcode Cancel Skill

Key Features

Use Cases

Pepcode Cancel Skill

Key Features

Use Cases