OpenParable
Skip to content
← Back to skills

Gsd:from Gsd2

Documents
gsd:from-gsd2

Gsd:from Gsd2 is an Agent Skill for documents published in the davepoon/buildwithclaude repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/davepoon/buildwithclaude/blob/HEAD/plugins/gsd/skills/from-gsd2/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gsd-from-gsd2, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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).

  1. Locate the .gsd/ directory — check the current working directory (or --path argument):

    node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" from-gsd2 --dry-run
    

    If no .gsd/ is found, report the error and stop.

  2. Show the dry-run preview — present the full file list and migration statistics to the user. Ask for confirmation before writing anything.

  3. Run the migration after confirmation:

    node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" from-gsd2
    

    Use --force if .planning/ already exists and the user has confirmed overwrite.

  4. Report the result — show the filesWritten count, planningDir path, and the preview summary.