Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
<codex_skill_adapter>
$gsd-workstreams.$gsd-workstreams as {{GSD_ARGS}}.{{GSD_ARGS}} as empty.GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:
Parameter mapping:
header → headerquestion → question"Label" — description → {label: "Label", description: "description"}id from header: lowercase, replace spaces with underscoresBatched calls:
AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]Multi-select workaround:
multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.Execute mode fallback:
request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.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> blocksParallel fan-out:
wait(ids) for all to completeResult parsing:
CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.close_agent(id) after collecting results from each agent
</codex_skill_adapter>Manage parallel workstreams for concurrent milestone work.
/gsd-workstreams [subcommand] [args]
| 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 |
Parse the user's input to determine which workstream operation to perform.
If no subcommand given, default to list.
Run: node "$GSD_TOOLS" workstream list --raw --cwd "$CWD"
Display the workstreams in a table format showing name, status, current phase, and progress.
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 milestoneRun: node "$GSD_TOOLS" workstream status <name> --raw --cwd "$CWD"
Display detailed phase breakdown and state information.
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.
Run: node "$GSD_TOOLS" workstream progress --raw --cwd "$CWD"
Display a progress overview across all workstreams.
Run: node "$GSD_TOOLS" workstream complete <name> --raw --cwd "$CWD"
Archive the workstream to milestones/.
Set the workstream as active and suggest /gsd-resume-work --ws <name>.
Format the JSON output from gsd-tools into a human-readable display.
Include the ${GSD_WS} flag in any routing suggestions.