Advances GSD workflow automation to the next task.

Install

mkdir -p .claude/skills/gsd-next-andreashxc && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13021" && unzip -o skill.zip -d .claude/skills/gsd-next-andreashxc && rm skill.zip

Installs to .claude/skills/gsd-next-andreashxc

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.

Automatically advance to the next logical step in the GSD workflow
66 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Advance the GSD workflow to the next logical step
  • Read STATE.md and ROADMAP.md to determine the next step
  • Scan prior phases for incomplete work
  • Bypass safety gates with a --force flag
  • Translate Task() to spawn_agent

How it works

This skill detects the current project state by reading STATE.md and ROADMAP.md, then invokes the next logical GSD workflow step. It translates GSD workflow syntax like AskUserQuestion and Task() into Codex equivalents.

Inputs & outputs

You give it
User text after $gsd-next, or no arguments
You get back
Execution of the next workflow step or a structured report of incomplete work

When to use gsd-next

  • Advancing workflow steps
  • Executing GSD agent tasks
  • Moving to the next stage of automation

About this skill

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-next.
  • Treat all user text after $gsd-next 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. spawn_agent has no inline model parameter; GSD embeds the resolved per-agent model directly into each agent's .toml at install time so model_overrides from .planning/config.json and ~/.gsd/defaults.json are honored automatically by Codex's agent router.
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks

Spawn restriction:

  • Codex restricts spawn_agent to cases where the user has explicitly requested sub-agents. When automatic spawning is not permitted, do the work inline in the current agent rather than attempting to force a spawn.

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> Detect the current project state and automatically invoke the next logical GSD workflow step. No arguments needed — reads STATE.md, ROADMAP.md, and phase directories to determine what comes next.

Designed for rapid multi-project workflows where remembering which phase/step you're on is overhead.

Supports --force flag to bypass safety gates (checkpoint, error state, verification failures, and prior-phase completeness scan).

Before routing to the next step, scans all prior phases for incomplete work: plans that ran without producing summaries, verification failures without overrides, and phases where discussion happened but planning never ran. When incomplete work is found, shows a structured report and offers three options: defer the gaps to the backlog and continue, stop and resolve manually, or force advance without recording. When prior phases are clean, routes silently with no interruption. </objective>

<execution_context> @/Users/andreas/Library/Mobile Documents/comappleCloudDocs/Code/gsd-test/.codex/get-shit-done/workflows/next.md </execution_context>

<process> Execute the next workflow from @/Users/andreas/Library/Mobile Documents/com~apple~CloudDocs/Code/gsd-test/.codex/get-shit-done/workflows/next.md end-to-end. </process>

When not to use it

  • When the user has not explicitly requested sub-agents for spawning
  • When the user needs to manually resolve incomplete work from prior phases

Limitations

  • Automatic spawning of sub-agents is restricted to cases where the user has explicitly requested them
  • The skill does not resolve incomplete work from prior phases automatically

How it compares

This workflow automatically determines and executes the next step based on project state, unlike manual progression through GSD phases.

Compared to similar skills

gsd-next side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
gsd-next (this skill)03moNo flagsIntermediate
using-superpowers953moNo flagsBeginner
ultrawork112moNo flagsAdvanced
clawhub252moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

using-superpowers

obra

Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists

95205

ultrawork

Yeachan-Heo

Parallel execution engine for high-throughput task completion

11184

clawhub

openclaw

Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawhub CLI.

25151

skill-installer

openai

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

29141

continuous-learning

affaan-m

Automatically extract reusable patterns from Claude Code sessions and save them as learned skills for future use.

995

memory-keeper-proactive-context-maintenance

b4CU-R4U

Automatically detect and maintain memory freshness by monitoring context staleness, significant code changes, task completions, and phase transitions. Proactively suggests and executes memory sync operations with user confirmation. Use when the user says "sync memory", "update context", or when the Skill detects that context is stale (>2 hours), significant changes have occurred (new commits), tasks completed, or major milestones reached. Replaces passive "context is stale" warnings with active maintenance.

694

Search skills

Search the agent skills registry