B. AskUserQuestion → request_user_input Mapping
GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:
Parameter mapping:
header → header
question → question
- 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
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.
1---2name: gsd-next3description: Automatically advance to the next logical step in the GSD workflow4---56<codex_skill_adapter>7## A. Skill Invocation8- This skill is invoked by mentioning `$gsd-next`.9- Treat all user text after `$gsd-next` as `{{GSD_ARGS}}`.10- If no arguments are present, treat `{{GSD_ARGS}}` as empty.1112## B. AskUserQuestion → request_user_input Mapping13GSD workflows use `AskUserQuestion` (Claude Code syntax). Translate to Codex `request_user_input`:1415Parameter mapping:16- `header` → `header`17- `question` → `question`18- Options formatted as `"Label" — description` → `{label: "Label", description: "description"}`19- Generate `id` from header: lowercase, replace spaces with underscores2021Batched calls:22- `AskUserQuestion([q1, q2])` → single `request_user_input` with multiple entries in `questions[]`2324Multi-select workaround:25- Codex has no `multiSelect`. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.2627Execute mode fallback:28- When `request_user_input` is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.2930## C. Task() → spawn_agent Mapping31GSD workflows use `Task(...)` (Claude Code syntax). Translate to Codex collaboration tools:3233Direct mapping:34- `Task(subagent_type="X", prompt="Y")` → `spawn_agent(agent_type="X", message="Y")`35- `Task(model="...")` → omit (Codex uses per-role config, not inline model selection)36- `fork_context: false` by default — GSD agents load their own context via `<files_to_read>` blocks3738Parallel fan-out:39- Spawn multiple agents → collect agent IDs → `wait(ids)` for all to complete4041Result parsing:42- Look for structured markers in agent output: `CHECKPOINT`, `PLAN COMPLETE`, `SUMMARY`, etc.43- `close_agent(id)` after collecting results from each agent44</codex_skill_adapter>4546<objective>47Detect the current project state and automatically invoke the next logical GSD workflow step.48No arguments needed — reads STATE.md, ROADMAP.md, and phase directories to determine what comes next.4950Designed for rapid multi-project workflows where remembering which phase/step you're on is overhead.5152Supports `--force` flag to bypass safety gates (checkpoint, error state, verification failures, and prior-phase completeness scan).5354Before 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.55</objective>5657<execution_context>58@/home/delorenj/code/bhappy/.codex/get-shit-done/workflows/next.md59</execution_context>6061<process>62Execute the next workflow from @/home/delorenj/code/bhappy/.codex/get-shit-done/workflows/next.md end-to-end.63</process>