from-gsd2

SkillDev tools

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

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the from-gsd2 skill

What this skill tells your AI

The instructions your AI receives, as published by buildomator/buildomator in skills/from-gsd2/SKILL.md and read by ahel’s review.

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 bm-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 "${CLAUDE_PLUGIN_ROOT:-$(ls -d "$HOME/.claude/plugins/cache/gsd-plugin/gsd/"*/ 2>/dev/null|sort -V|tail -1)}/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 "${CLAUDE_PLUGIN_ROOT:-$(ls -d "$HOME/.claude/plugins/cache/gsd-plugin/gsd/"*/ 2>/dev/null|sort -V|tail -1)}/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.

Signals

GitHub stars
86
Forks
12
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
from-gsd2
Source
github.com/buildomator/buildomator