gsd-new-milestone

<codex_skill_adapter>

A. Skill Invocation

• This skill is invoked by mentioning $gsd-new-milestone.
• Treat all user text after $gsd-new-milestone 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> Start a new milestone: questioning → research (optional) → requirements → roadmap.

Brownfield equivalent of new-project. Project exists, PROJECT.md has history. Gathers "what's next", updates PROJECT.md, then runs requirements → roadmap cycle.

Creates/Updates:

• .planning/PROJECT.md — updated with new milestone goals
• .planning/research/ — domain research (optional, NEW features only)
• .planning/REQUIREMENTS.md — scoped requirements for this milestone
• .planning/ROADMAP.md — phase structure (continues numbering)
• .planning/STATE.md — reset for new milestone

After: $gsd-plan-phase [N] to start execution. </objective>

<execution_context> @C:/dev/endless-crystal/.codex/get-shit-done/workflows/new-milestone.md @C:/dev/endless-crystal/.codex/get-shit-done/references/questioning.md @C:/dev/endless-crystal/.codex/get-shit-done/references/ui-brand.md @C:/dev/endless-crystal/.codex/get-shit-done/templates/project.md @C:/dev/endless-crystal/.codex/get-shit-done/templates/requirements.md </execution_context>

<context> Milestone name: {{GSD_ARGS}} (optional - will prompt if not provided)

Project and milestone context files are resolved inside the workflow (init new-milestone) and delegated via <files_to_read> blocks where subagents are used. </context>

<process> Execute the new-milestone workflow from @C:/dev/endless-crystal/.codex/get-shit-done/workflows/new-milestone.md end-to-end. Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits). </process>