dev-cancel

Stop active multi-phase engineering workflows and produce a structured cancel report.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-cancel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-cancel
Source: https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/dev-cancel
Command: npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-cancel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a safe, repeatable way to stop active multi-phase engineering workflows when a user requests cancellation, preventing accidental continuation, deletion, or cross-layer cascade while preserving the work produced so far.

Core Features & Use Cases

  • Detect active engineering flows: recognizes dev-autopilot, dev-deep-interview, dev-plan, dev-ralplan, and similar multi-phase agents or planner/executor activity.
  • Safe halt semantics: stops the flow immediately without calling further agents, continuing phases, or deleting artifacts.
  • Structured cancel report: produces a clear summary of completed phases, in-progress work, not-started phases, artifact locations, recommended next steps, and open questions for resumption.
  • Use cases: a developer types "cancel" mid-run of dev-autopilot; a user aborts an interview loop; an operator needs to stop a planner due to changed requirements.

Quick Start

Cancel the active dev-autopilot or dev-plan workflow and return a structured Engineering Layer Cancel Report listing completed, in-progress, and not-started phases, preserved artifact locations, and a recommended next step.

Frequently Asked Questions about dev-cancel

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

FAQPage Schema
How do I stop a multi-phase engineering workflow without losing artifacts?

Stop a multi-phase engineering workflow safely by halting all agent actions immediately without deleting artifacts. This preserves completed work and workspace files, preventing accidental continuation or cross-layer cascade while generating a structured cancel report.

Can I cancel dev-autopilot mid-run and keep the files it already generated?

Yes, you can cancel dev-autopilot mid-run and keep generated files. The cancellation process halts all active agents immediately without triggering further phases, preserving all workspace artifacts and files produced before the abort.

What happens to in-progress phases when I abort a dev-plan workflow?

When you abort a dev-plan workflow, in-progress phases are halted immediately and summarized in a structured cancel report. The report details completed, in-progress, and not-started phases alongside artifact locations and recommended next steps for resumption.

Does cancelling an engineering flow trigger other agents to clean up?

No, cancelling an engineering flow applies safe halt semantics that stop all actions immediately without invoking further agents. This prevents cross-layer cascade and ensures the workflow terminates cleanly without triggering automated cleanup or continuation.

What is included in the structured cancel report after stopping a workflow?

The structured cancel report includes a summary of completed, in-progress, and not-started phases. It also lists preserved artifact locations, recommended next steps for resumption, and any open questions remaining from the halted engineering workflow.

When should I use a structured cancellation process instead of just closing the session?

Use a structured cancellation process when running multi-phase engineering workflows like dev-autopilot or deep interviews and you need to preserve artifacts. It prevents cross-layer cascade and data loss, whereas closing a session might leave agents running or work inaccessible.