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
Routes to the check-todos workflow which handles:
- Todo counting and listing with area filtering
- Interactive selection with full context loading
- Roadmap correlation checking
- Action routing (work now, add to phase, brainstorm, create phase)
- STATE.md updates and git commits
Todo state and roadmap correlation are loaded in-workflow using init todos and targeted reads.
The workflow handles all logic including:
- Todo existence checking
- Area filtering
- Interactive listing and selection
- Full context loading with file summaries
- Roadmap correlation checking
- Action offering and execution
- STATE.md updates
- Git commits
1---2name: gsd-check-todos3description: List pending todos and select one to work on4---56<codex_skill_adapter>7## A. Skill Invocation8- This skill is invoked by mentioning `$gsd-check-todos`.9- Treat all user text after `$gsd-check-todos` 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>47List all pending todos, allow selection, load full context for the selected todo, and route to appropriate action.4849Routes to the check-todos workflow which handles:50- Todo counting and listing with area filtering51- Interactive selection with full context loading52- Roadmap correlation checking53- Action routing (work now, add to phase, brainstorm, create phase)54- STATE.md updates and git commits55</objective>5657<execution_context>58@/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/workflows/check-todos.md59</execution_context>6061<context>62Arguments: {{GSD_ARGS}} (optional area filter)6364Todo state and roadmap correlation are loaded in-workflow using `init todos` and targeted reads.65</context>6667<process>68**Follow the check-todos workflow** from `@/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/workflows/check-todos.md`.6970The workflow handles all logic including:711. Todo existence checking722. Area filtering733. Interactive listing and selection744. Full context loading with file summaries755. Roadmap correlation checking766. Action offering and execution777. STATE.md updates788. Git commits79</process>