gsd-phase

name	gsd-phase
description	CRUD for phases in ROADMAP.md — add, insert, remove, or edit phases
metadata	{"short-description":"CRUD for phases in ROADMAP.md — add, insert, remove, or edit phases"}

<codex_skill_adapter>

A. Skill Invocation

• This skill is invoked by mentioning $gsd-phase.
• Treat all user text after $gsd-phase 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, activate TEXT_MODE: append --text to {{GSD_ARGS}} so the workflow's built-in text-mode branching takes over. Present every AskUserQuestion call as a plain-text numbered list, then stop and wait for the user's reply. Do NOT pick a default and continue (#3018 / #3808).
• 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.

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")
• Agent(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.
• Resolved reasoning_effort="low|medium|high|xhigh" (xhigh is a GSD/Codex tier, not a generic runtime enum) → pass reasoning_effort to spawn_agent when the runtime/tool supports it. Omit missing, empty, inherited, or unsupported values; do not invent one-off effort literals in workflow prose.
• fork_context: false by default — GSD agents load their own context via <files_to_read> blocks
• Task(isolation="worktree") / Agent(isolation="worktree") → no direct Codex mapping. Codex spawn_agent does not create or bind a git worktree automatically. Workflows that require this isolation must fail closed or use an explicit manual worktree protocol before spawning (#3360).

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.
• In some Codex sessions, multi-agent tooling can be deferred. If spawn_agent is not currently visible, discover tools first via tool_search before defaulting to inline execution.

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>

Manage phases in ROADMAP.md with a single consolidated command.

Mode routing:

• default (no flag): Add a new integer phase to the end of the current milestone → add-phase workflow
• --insert: Insert urgent work as a decimal phase (e.g., 72.1) between existing phases → insert-phase workflow
• --remove: Remove a future phase and renumber subsequent phases → remove-phase workflow
• --edit: Edit any field of an existing phase in place → edit-phase workflow

Flag	Action	Workflow
(none)	Add new integer phase at end of milestone	add-phase
--insert	Insert decimal phase (e.g., 72.1) after specified phase	insert-phase
--remove	Remove future phase, renumber subsequent	remove-phase
--edit	Edit fields of existing phase in place	edit-phase

<execution_context> @D:/Projects/pjmagee/multi-stream-viewer/.codex/gsd-core/workflows/add-phase.md @D:/Projects/pjmagee/multi-stream-viewer/.codex/gsd-core/workflows/insert-phase.md @D:/Projects/pjmagee/multi-stream-viewer/.codex/gsd-core/workflows/remove-phase.md @D:/Projects/pjmagee/multi-stream-viewer/.codex/gsd-core/workflows/edit-phase.md </execution_context>

Arguments: {{GSD_ARGS}}

Parse the first token of {{GSD_ARGS}}:

• If it is --insert: strip the flag, pass remainder (format: ) to insert-phase workflow
• If it is --remove: strip the flag, pass remainder (phase number) to remove-phase workflow
• If it is --edit: strip the flag, pass remainder (phase-number [--force]) to edit-phase workflow
• Otherwise: pass all of {{GSD_ARGS}} (phase description) to add-phase workflow

Roadmap and state are resolved in-workflow via init phase-op and targeted reads.

1. Parse the leading flag (if any) from {{GSD_ARGS}}. 2. Load and execute the appropriate workflow end-to-end based on the routing table above. 3. Preserve all validation gates from the target workflow.