gsd-execute-phase

name	gsd-execute-phase
description	Execute all plans in a phase with wave-based parallelization
metadata	{"short-description":"Execute all plans in a phase with wave-based parallelization"}

<codex_skill_adapter>

A. Skill Invocation

• This skill is invoked by mentioning $gsd-execute-phase.
• Treat all user text after $gsd-execute-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:

• 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 </codex_skill_adapter>

Execute all plans in a phase using wave-based parallel execution.

Orchestrator stays lean: discover plans, analyze dependencies, group into waves, spawn subagents, collect results. Each subagent loads the full execute-plan context and handles its own plan.

Context budget: ~15% orchestrator, 100% fresh per subagent.

<execution_context> @/Users/teo/src/tempo/.codex/get-shit-done/workflows/execute-phase.md @/Users/teo/src/tempo/.codex/get-shit-done/references/ui-brand.md </execution_context>

Phase: {{GSD_ARGS}}

Flags:

• --gaps-only — Execute only gap closure plans (plans with gap_closure: true in frontmatter). Use after verify-work creates fix plans.

Context files are resolved inside the workflow via gsd-tools init execute-phase and per-subagent <files_to_read> blocks.

Execute the execute-phase workflow from @/Users/teo/src/tempo/.codex/get-shit-done/workflows/execute-phase.md end-to-end. Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing).