dev-cancel

Canceling an active development pipeline stops further agent execution immediately and preserves existing spec and plan artifacts. It produces a structured cancel report detailing completed phases, in-progress work, and recommended next steps for manual resumption.

When you cancel an active development pipeline, all spec and plan artifacts are preserved intact. The cancellation process focuses on the engineering layer, keeping workspace files secure so you can manually resume work later without losing completed phases.

Yes, you can cancel dev-autopilot or dev-plan routines without affecting the business layer. The cancellation scope is strictly bounded to the engineering layer, preventing cascading cancellations from impacting business routines or unrelated workflows.

The engineering layer cancel report includes a structured summary of completed phases, in-progress work, and not-started phases. It also points to where workspace files live and provides a recommended next step for resuming the development workflow manually.

Yes, workflow cancellation supports multi-phase pipelines like dev-deep-interview, dev-autopilot, and dev-plan. The system detects the active flow and its current phase to stop agent execution cleanly and report exactly what remains to be done.

You should not use automated cancellation if you need to continue the current phase to completion, as it stops further agent execution immediately. It is designed for clean exits from multi-phase engineering routines, not for pausing individual steps.