gsd:remove-phase
Remove a future phase from roadmap and renumber subsequent phases
Profile →npx skills add davepoon/buildwithclaude --skill remove-phase --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<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> @${CLAUDE_PLUGIN_ROOT}/workflows/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 @${CLAUDE_PLUGIN_ROOT}/workflows/remove-phase.md end-to-end. Preserve all validation gates (future phase check, work check), renumbering logic, and commit. </process>
What does the gsd:remove-phase skill do?
Remove a future phase from roadmap and renumber subsequent phases
How do I install it?
Run `npx skills add davepoon/buildwithclaude --skill remove-phase --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.