gsd-from-gsd2

name	gsd-from-gsd2
description	Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format
metadata	{"short-description":"Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format"}

<codex_skill_adapter>

A. Skill Invocation

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

Reverse-migrate a GSD-2 project (`.gsd/` directory) back to GSD v1 (`.planning/`) format. - The migration is non-destructive: `.gsd/` is never modified or removed. - Pass `--path ` to migrate a project at a different path than the current directory. - Slices are numbered sequentially across all milestones (M001/S01 → phase 01, M001/S02 → phase 02, M002/S01 → phase 03, etc.). - Tasks within each slice become plans (T01 → plan 01, T02 → plan 02, etc.). - Completed slices and tasks carry their done state into ROADMAP.md checkboxes and SUMMARY.md files. - GSD-2 cost/token ledger, database state, and VS Code extension state cannot be migrated.