Gustavosareto/gsd-workstreams

<codex_skill_adapter>

A. Skill Invocation

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

/gsd-workstreams

Manage parallel workstreams for concurrent milestone work.

Usage

/gsd-workstreams [subcommand] [args]

Subcommands

| Command | Description | |---------|-------------| | list | List all workstreams with status | | create <name> | Create a new workstream | | status <name> | Detailed status for one workstream | | switch <name> | Set active workstream | | progress | Progress summary across all workstreams | | complete <name> | Archive a completed workstream | | resume <name> | Resume work in a workstream |

Step 1: Parse Subcommand

Parse the user's input to determine which workstream operation to perform. If no subcommand given, default to list.

Step 2: Execute Operation

list

Run: node "$GSD_TOOLS" workstream list --raw --cwd "$CWD" Display the workstreams in a table format showing name, status, current phase, and progress.

create

Run: node "$GSD_TOOLS" workstream create <name> --raw --cwd "$CWD" After creation, display the new workstream path and suggest next steps:

• /gsd-new-milestone --ws <name> to set up the milestone

status

Run: node "$GSD_TOOLS" workstream status <name> --raw --cwd "$CWD" Display detailed phase breakdown and state information.

switch

Run: node "$GSD_TOOLS" workstream set <name> --raw --cwd "$CWD" Also set GSD_WORKSTREAM for the current session when the runtime supports it. If the runtime exposes a session identifier, GSD also stores the active workstream session-locally so concurrent sessions do not overwrite each other.

progress

Run: node "$GSD_TOOLS" workstream progress --raw --cwd "$CWD" Display a progress overview across all workstreams.

complete

Run: node "$GSD_TOOLS" workstream complete <name> --raw --cwd "$CWD" Archive the workstream to milestones/.

resume

Set the workstream as active and suggest /gsd-resume-work --ws <name>.

Step 3: Display Results

Format the JSON output from gsd-tools into a human-readable display. Include the ${GSD_WS} flag in any routing suggestions.