gsd-from-gsd2
Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format
- License 许可
- Apache-2.0
- 最近更新
- 2026-07-15
- Stars
- ★ 15
- Forks
- 1
01 前言 Front Matter
- name
- gsd-from-gsd2
- metadata
- { "short-description": "Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format" }
- description
- Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format
03 SKILL.md 正文
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-from-gsd2. - Treat all user text after
$gsd-from-gsd2as{{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>
<objective>
Reverse-migrate a GSD-2 project (.gsd/ directory) back to GSD v1 (.planning/) format.
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. </objective>
<process>
-
Locate the .gsd/ directory — check the current working directory (or
--pathargument):node "E:/NER/.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 "E:/NER/.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.
</process>
<notes>
- The migration is non-destructive:
.gsd/is never modified or removed. - Pass
--path <dir>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. </notes>
04 同仓库更多 Skills
deploy-app
Deploy the application to staging or production environments.
deploy
Deploy the application to environments.
building-native-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
create-section
Use when creating a new section for the AI Workshop presentation. Guides through title slide setup, layout choices, and content gathering. Activates when user wants to add a new topic section to the slideshow.
ship-checker
Run a full pre-ship review for this repo. Use when asked if a change is ready to deploy, publish, or ship.
lint-check
Run repository linters and report failures.