gsd-autonomous

<codex_skill_adapter>

A. Skill Invocation

• This skill is invoked by mentioning $gsd-autonomous.
• Treat all user text after $gsd-autonomous 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. 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> Execute all remaining milestone phases autonomously. For each phase: discuss → plan → execute. Pauses only for user decisions (grey area acceptance, blockers, validation requests).

Uses ROADMAP.md phase discovery and Skill() flat invocations for each phase command. After all phases complete: milestone audit → complete → cleanup.

Creates/Updates:

• .planning/STATE.md — updated after each phase
• .planning/ROADMAP.md — progress updated after each phase
• Phase artifacts — CONTEXT.md, PLANs, SUMMARYs per phase

After: Milestone is complete and cleaned up. </objective>

<execution_context> @C:/Users/simon/Documents/GitHub/scrimflow/.codex/get-shit-done/workflows/autonomous.md @C:/Users/simon/Documents/GitHub/scrimflow/.codex/get-shit-done/references/ui-brand.md </execution_context>

<context> Optional flags:

• --from N — start from phase N instead of the first incomplete phase.
• --to N — stop after phase N completes (halt instead of advancing to next phase).
• --only N — execute only phase N (single-phase mode).
• --interactive — run discuss inline with questions (not auto-answered), then dispatch plan→execute as background agents. Keeps the main context lean while preserving user input on decisions.

Project context, phase list, and state are resolved inside the workflow using init commands (gsd-sdk query init.milestone-op, gsd-sdk query roadmap.analyze). No upfront context loading needed. </context>

<process> Execute the autonomous workflow from @C:/Users/simon/Documents/GitHub/scrimflow/.codex/get-shit-done/workflows/autonomous.md end-to-end. Preserve all workflow gates (phase discovery, per-phase execution, blocker handling, progress display). </process>