gsd-add-phase

Imported from huathanhnam95-del/demoproject (.claude/skills/gsd-add-phase/SKILL.md). Install upstream with npx skills add huathanhnam95-del/demoproject --skill gsd-add-phase. Copyright stays with the author.

<codex_skill_adapter>

A. Skill Invocation

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

Routes to the add-phase workflow which handles:

• Phase number calculation (next sequential integer)
• Directory creation with slug generation
• Roadmap structure updates
• STATE.md roadmap evolution tracking

<execution_context> @C:/Users/Admin/.codex/get-shit-done/workflows/add-phase.md </execution_context>

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

The workflow handles all logic including:

1. Argument parsing and validation
2. Roadmap existence checking
3. Current milestone identification
4. Next phase number calculation (ignoring decimals)
5. Slug generation from description
6. Phase directory creation
7. Roadmap entry insertion
8. STATE.md updates