Removes an unstarted future phase from the roadmap and renumbers every subsequent phase for a clean linear sequence. Use to drop planned work that is no longer needed. Refuses started or completed phases. --dry-run previews the deletion and renumbering without changing anything.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add D0NMEGA/donnyclaude --skill donny-remove-phase --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Donny Remove Phase?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/d0nmega-donny-remove-phase)More formats (shields.io, HTML) on the badges page.
---
name: donny-remove-phase
description: "Removes an unstarted future phase from the roadmap and renumbers every subsequent phase for a clean linear sequence. Use to drop planned work that is no longer needed. Refuses started or completed phases. --dry-run previews the deletion and renumbering without changing anything."
argument-hint: "<phase-number> [--dry-run]"
disable-model-invocation: true
allowed-tools:
- Read
- Write
- Bash
- Glob
---
<objective>
Remove an unstarted future phase from the roadmap and renumber all subsequent phases to maintain a clean, linear sequence.
Purpose: Clean removal of work that is no longer needed, without polluting context with cancelled/deferred markers.
Output: Phase deleted, all subsequent phases renumbered, git commit as historical record.
</objective>
<execution_context>
@~/.claude/donny/workflows/remove-phase.md
</execution_context>
<context>
Phase: $ARGUMENTS - phase number to remove, plus optional `--dry-run`.
- `--dry-run` - preview the deletion and renumbering, then exit without changing or committing anything.
Roadmap and state are resolved in-workflow via `init phase-op` and targeted reads.
</context>
<process>
Execute the remove-phase workflow from @~/.claude/donny/workflows/remove-phase.md end-to-end.
Preserve all validation gates (future phase check, work check), the `--dry-run` preview gate, renumbering logic, and commit.
</process>
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.