gsd-ship

<gsd_agent_plugin_adapter> This GSD distribution is loaded from an Agent Plugin rather than a fixed runtime home.

• Resolve GSD_PLUGIN_ROOT as the absolute directory two levels above this SKILL.md.
• Resolve every @../../... execution-context reference relative to this skill directory.
• Before running a workflow shell command, replace gsd-sdk with node "$GSD_PLUGIN_ROOT/bin/gsd-sdk.js" and turn any ../../get-shit-done/... command path into an absolute path below $GSD_PLUGIN_ROOT.
• Named GSD agent prompts live in $GSD_PLUGIN_ROOT/agents/. If the runtime has no matching registered agent type, spawn an available generic worker/default agent and include the corresponding agents/<name>.md prompt in its task message. </gsd_agent_plugin_adapter>

<codex_skill_adapter>

A. Skill Invocation

• This skill is invoked by mentioning $gsd-ship.
• Treat all user text after $gsd-ship 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 or unavailable, you MUST stop and present the questions as a plain-text numbered list, then wait for the user's reply. Do NOT pick a default and continue (#3018).
• You may only proceed without a user answer when one of these is true: (a) the invocation included an explicit non-interactive flag (--auto or --all), (b) the user has explicitly approved a specific default for this question, or (c) the workflow's documented contract says defaults are safe (e.g. autonomous lifecycle paths).
• Do NOT write workflow artifacts (CONTEXT.md, DISCUSSION-LOG.md, PLAN.md, checkpoint files) until the user has answered the plain-text questions or one of (a)-(c) above applies. Surfacing the questions and waiting is the correct response — silently defaulting and writing artifacts is the #3018 failure mode.