Skip to content
Skills Library
Programming · Automation

dev-cancel

/dev-cancel

Cleanly stop an active engineering layer flow (dev-autopilot, dev-deep-interview, dev-plan) and report what was completed. Use when the user says "cancel", "stop", "abort", "cancelomc", or wants to exit a multi-phase dev workflow.

Repository
evo-nexus ↗
Licence
Apache-2.0
Last repository change
12.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.05.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Cleanly stop an active engineering layer flow (dev-autopilot, dev-deep-interview, dev-plan) and report what was completed. Use when the user says "cancel", "stop", "abort", "cancelomc", or wants to exit a multi-phase dev workflow.

Triggers from the description

cancelstopabortcancelomc
Original author description

Cleanly stop an active engineering layer flow (dev-autopilot, dev-deep-interview, dev-plan) and report what was completed. Use when the user says "cancel", "stop", "abort", "cancelomc", or wants to exit a multi-phase dev workflow.

How it works

  1. Use When
  2. Do Not Use When
  3. Goal
  4. Workflow
  5. Rules
  6. Failure Modes To Avoid
Original SKILL.md headings · 83 lines, 485 words
SKILL.md preview
---
name: dev-cancel
description: Cleanly stop an active engineering layer flow (dev-autopilot, dev-deep-interview, dev-plan) and report what was completed. Use when the user says "cancel", "stop", "abort", "cancelomc", or wants to exit a multi-phase dev workflow.
---

# Dev Cancel

Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer — simplified, runtime-free version.

## Use When
- User says "cancel", "stop", "abort", "cancelomc", "stopomc"
- Multi-phase workflow (dev-autopilot, dev-deep-interview, dev-plan, dev-ralplan) is active and the user wants to exit
- Context indicates a long-running dev orchestration that needs a clean stop

## Do Not Use When
- No engineering layer flow is active — just respond conversationally
- The user is canceling a single tool call (Claude Code already handles that)
- The user wants to pause/resume → use the workflow's own pause mechanism instead

## Goal
Stop the active flow cleanly and give the user a structured summary of:
1. **What was completed** before cancel
2. **What was in progress** at cancel time
3. **What was not started**
4. **Where the artifacts live** (spec, plan, code) so the user can resume manually
5. **Recommended next step**

## Workflow

### 1. Detect Active Flow
Look at recent context for signals:
- `dev-autopilot` was invoked → multi-phase pipeline active
- `dev-deep-interview` was invoked → interview loop active
- `dev-plan` was invoked → planning session active
- A `@compass-planner`, `@bolt-executor`, etc. agent was running

### 2. Stop the Flow
- Do NOT call any further agents
- Do NOT continue any in-progress phase
- Do NOT delete artifacts (specs, plans, partial code) — preserve for user inspection

### 3. Generate Cancel Report
Output this structure:

```markdown
## Engineering Layer Cancel Report

**Flow stopped:** {dev-autopilot | dev-deep-interview | dev-plan | other}
**Stopped at phase:** {phase name}
**Reason:** {user request / error / explicit abort}

### Completed
- [phase 1: spec written → workspace/projects/specs/...]
- [phase 2: plan approved → workspace/projects/plans/...]

### In Progress (at cancel time)
- [phase X: implementing Y in file Z]

### Not Started
- [remaining phases]

### Artifacts Preserved
- Spec: `workspace/projects/specs/[C]autopilot-spec-{name}.md`
- Plan: `workspace/projects/plans/[C]autopilot-plan-{name}.md`
- Code changes: see `git status`

### Recommended Next Step
- "Resume manually": pick up from {phase} using {agent} directly
- "Re-run from scratch": delete artifacts and re-invoke `dev-autopilot`
- "Investigate first": review the artifacts before deciding

### Open Questions
[any unresolved decisions the flow was waiting on]
```

## Rules
- **Always preserve artifacts.** Never delete spec/plan files on cancel — the user may want to resume.
- **Never cascade cancels into business layer.** Cancel only stops engineering flows; Clawdia/Flux/etc. routines keep running.
- **Be explicit about what's incomplete.** Don't claim partial work as done.
- **Suggest the cheapest resume path** — usually picking up from where the flow stopped, not restarting.

## Failure Modes To Avoid
- **Silent cancel**: stopping without a report. Always emit the structured summary.
- **Cleanup overreach**: deleting artifacts the user might want.
- **Continuing one more phase**: "let me just finish this last bit". No — stop means stop.
- **Vague status**: "I stopped the workflow." → useless. Always include phase, completed work, and next step.

Versions

The database has no other skills named dev-cancel.

Database snapshot: 13.11.2026 · package version cc0d19bed63b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100dev-autopilot
    Full autonomous execution from idea to working code. Use when user says "autopilot", "autonomous", "build me", "create me", "make me", "full auto" — orchestrates spec → plan → code → QA → validation across the engineering layer agents.
  • 100cancel
    Cancel any active OMG mode and clean up state. Activate when user says: cancel, stop, cancelomg, stopomg, abort, kill it, stop everything.
  • 100dev-deep-interview
    Socratic questioning to crystallize vague requirements into a testable spec. Use when input is ambiguous, when the user asks for "deep interview", or before dev-autopilot if the brief is too broad. Pairs with @echo-analyst.
  • 100sprint-workflow
    Use when starting a new feature, refactor, or multi-step dev task — runs the full sprint cycle (Think → Plan → Build → Review → Test → Ship → Monitor) using Copilot CLI's plan/autopilot modes.
  • 100autopilot
    Run one explicit bounded Blueprint spec and implementation pass through configured quality gates, then stop before completion or external actions. Use only when the user directly invokes /autopilot, $autopilot, or asks for Autopilot.
  • 90dev-implement
    Execute an approved plan task by task with a check after each file, log every deviation against the acceptance criteria, and apply stop rules for build and type errors. Use after the plan is approved, or when the user says "làm đi" on a planned change, or when a build/typecheck/lint keeps failing.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.