mindforge-remove-phase
The mindforge-remove-phase skill deletes an unstarted future phase from a project roadmap and automatically renumbers all subsequent phases to maintain sequential ordering. Use this when you've decided to eliminate planned work and want a clean removal without leaving cancelled markers in the project context, with changes recorded as a git commit for historical tracking.
git clone --depth 1 https://github.com/sairam0424/MindForge /tmp/mindforge-remove-phase && cp -r /tmp/mindforge-remove-phase/.agent/skills/mindforge-remove-phase ~/.claude/skills/mindforge-remove-phaseSKILL.md
<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 you've decided not to do, without polluting context with cancelled/deferred markers. Output: Phase deleted, all subsequent phases renumbered, git commit as historical record. </objective> <execution_context> @.agent/workflows/mindforge-remove-phase.md </execution_context> <context> Phase: $ARGUMENTS Roadmap and state are resolved in-workflow via `init phase-op` and targeted reads. </context> <process> Execute the remove-phase workflow from @.agent/workflows/mindforge-remove-phase.md end-to-end. Preserve all validation gates (future phase check, work check), renumbering logic, and commit. </process>
Publish a skill to the npm registry (or private registry).
Add an idea to the backlog parking lot (999.x numbering)
Add phase to end of current milestone in roadmap
Generate tests for a completed phase based on UAT criteria and implementation
Capture idea or task as todo from current conversation context
Audit milestone completion against original intent before archiving
Cross-phase audit of all outstanding UAT and verification items
Run all remaining phases autonomously — discuss→plan→execute per phase