gsd-from-gsd2
Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format
SKILL.md.codex/skills/gsd-from-gsd2/SKILL.md
GitHub<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→headerquestion→question- Options formatted as
"Label" — description→{label: "Label", description: "description"} - Generate
idfrom header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2])→ singlerequest_user_inputwith multiple entries inquestions[]
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_inputis 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: falseby 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>
Maps the GSD-2 hierarchy (Milestone → Slice → Task) to the GSD v1 hierarchy (Milestone sections in ROADMAP.md → Phase → Plan), preserving completion state, research files, and summaries.
CJS-only: from-gsd2 is not on the gsd-sdk query registry; call gsd-tools.cjs as shown below (see docs/CLI-TOOLS.md).
</objective>
Locate the .gsd/ directory — check the current working directory (or
--pathargument):node "/Users/sasikumar/Documents/n8n/.codex/get-shit-done/bin/gsd-tools.cjs" from-gsd2 --dry-runIf no
.gsd/is found, report the error and stop.Show the dry-run preview — present the full file list and migration statistics to the user. Ask for confirmation before writing anything.
Run the migration after confirmation:
node "/Users/sasikumar/Documents/n8n/.codex/get-shit-done/bin/gsd-tools.cjs" from-gsd2Use
--forceif.planning/already exists and the user has confirmed overwrite.Report the result — show the
filesWrittencount,planningDirpath, and the preview summary.