Gsd Update

<codex_skill_adapter>

A. Skill Invocation

• This skill is invoked by mentioning $gsd-update.
• Treat all user text after $gsd-update 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> Check for GSD updates, install if available, and display what changed.

Routes to the update workflow which handles:

• Version detection (local vs global installation)
• npm version checking
• Changelog fetching and display
• User confirmation with clean install warning
• Update execution and cache clearing
• Restart reminder

</objective>

<execution_context> @C:/repositorios/libery.wallet/.codex/get-shit-done/workflows/update.md </execution_context>

<process> Follow the update workflow from @C:/repositorios/libery.wallet/.codex/get-shit-done/workflows/update.md.

The workflow handles all logic including: 1. Installed version detection (local/global) 2. Latest version checking via npm 3. Version comparison 4. Changelog fetching and extraction 5. Clean install warning display 6. User confirmation 7. Update execution 8. Cache clearing </process>