GS

gsd-remove-phase

Updates project roadmap by removing and reindexing phases.

Install

mkdir -p .claude/skills/gsd-remove-phase-maxkrivich && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13649" && unzip -o skill.zip -d .claude/skills/gsd-remove-phase-maxkrivich && rm skill.zip

Installs to .claude/skills/gsd-remove-phase-maxkrivich

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Remove a future phase from roadmap and renumber subsequent phases
65 charsno explicit “when” trigger
Beginner

Key capabilities

  • Remove an unstarted future phase from the roadmap.
  • Renumber all subsequent phases.
  • Maintain a clean, linear sequence of phases.
  • Preserve validation gates.
  • Create a git commit as a historical record.

How it works

The skill executes a remove-phase workflow that deletes an unstarted future phase from the roadmap, renumbers all subsequent phases to maintain sequence, and records the change with a git commit.

Inputs & outputs

You give it
The phase to be removed, specified by arguments.
You get back
A roadmap with the specified phase removed, subsequent phases renumbered, and a git commit recording the change.

When to use gsd-remove-phase

  • Updating project scope
  • Removing outdated phases

About this skill

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-remove-phase.
  • Treat all user text after $gsd-remove-phase as {{GSD_ARGS}}.
  • If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

  • headerheader
  • questionquestion
  • Options formatted as "Label" — description{label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

  • Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

  • When request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

  • Task(subagent_type="X", prompt="Y")spawn_agent(agent_type="X", message="Y")
  • Task(model="...") → omit (Codex uses per-role config, not inline model selection)
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks

Parallel fan-out:

  • Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

  • Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
  • close_agent(id) after collecting results from each agent </codex_skill_adapter>
<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> @/Users/max.kryvych/Projects/frontgate/.codex/get-shit-done/workflows/remove-phase.md </execution_context>

<context> Phase: {{GSD_ARGS}}

Roadmap and state are resolved in-workflow via init phase-op and targeted reads. </context>

<process> Execute the remove-phase workflow from @/Users/max.kryvych/Projects/frontgate/.codex/get-shit-done/workflows/remove-phase.md end-to-end. Preserve all validation gates (future phase check, work check), renumbering logic, and commit. </process>

When not to use it

  • When the phase to be removed has already started or is completed.
  • When the goal is to defer a phase rather than remove it.

Limitations

  • The skill only removes unstarted future phases.
  • The skill relies on the roadmap and state being resolved in-workflow.
  • The skill does not support inline model selection for spawned agents.

How it compares

This skill automates the removal of a future phase and the renumbering of subsequent phases, ensuring a clean and consistent roadmap without manual adjustments or polluting context with cancelled markers.

Compared to similar skills

gsd-remove-phase side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
gsd-remove-phase (this skill)04moNo flagsBeginner
planning-with-files2336moReviewIntermediate
trello413moReviewBeginner
pmbok-project-management389moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

planning-with-files

davila7

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

233106

trello

openclaw

Manage Trello boards, lists, and cards via the Trello REST API.

41205

pmbok-project-management

jgtolentino

Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.

38183

clickup

civitai

Interact with ClickUp tasks and documents - get task details, view comments, create and manage tasks, create and edit docs. Use when working with ClickUp task/doc URLs or IDs.

37176

ma-playbook

alirezarezvani

M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.

39122

create-plan

antinomyhq

Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.

36121

Search skills

Search the agent skills registry