openspec-apply-change

<codex_skill_adapter>

A. Skill Invocation

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

<objective> Execute small, ad-hoc tasks with GSD guarantees (atomic commits, STATE.md tracking).

Quick mode is the same system with a shorter path:

• Spawns gsd-planner (quick mode) + gsd-executor(s)
• Quick tasks live in .planning/quick/ separate from planned phases
• Updates STATE.md "Quick Tasks Completed" table (NOT ROADMAP.md)

Default: Skips research, discussion, plan-checker, verifier. Use when you know exactly what to do.

--discuss flag: Lightweight discussion phase before planning. Surfaces assumptions, clarifies gray areas, captures decisions in CONTEXT.md. Use when the task has ambiguity worth resolving upfront.

--full flag: Enables the complete quality pipeline — discussion + research + plan-checking + verification. One flag for everything.

--validate flag: Enables plan-checking (max 2 iterations) and post-execution verification only. Use when you want quality guarantees without discussion or research.

--research flag: Spawns a focused research agent before planning. Investigates implementation approaches, library options, and pitfalls for the task. Use when you're unsure of the best approach.

Granular flags are composable: --discuss --research --validate gives the same result as --full. </objective>

<execution_context> @/Users/wilderherrera/Desktop/convision/.codex/get-shit-done/workflows/quick.md </execution_context>

<context> {{GSD_ARGS}}

Context files are resolved inside the workflow (init quick) and delegated via <files_to_read> blocks. </context>

<process> Execute the quick workflow from @/Users/wilderherrera/Desktop/convision/.codex/get-shit-done/workflows/quick.md end-to-end. Preserve all workflow gates (validation, task description, planning, execution, state updates, commits). </process>