Skill

gsd:from-gsd2

From gsd

Reverse-migrates GSD-2 (.gsd/) projects to GSD v1 (.planning/) format by mapping milestones/slices/tasks to roadmap phases/plans, preserving completion states, summaries, and research files.

Bash

npx claudepluginhub jnuyens/gsd-plugin --plugin gsd

Tool Access

This skill is limited to using the following tools:

ReadWriteBash

Preview

SKILL.md

Similar Skills

task-folder-migrator

Migrates single-file Markdown tasks to v3.0.0 folder structure with phased subfiles (task.md, research.md, etc.), parses content by headers, creates .bak backups. Auto or manual.

drupal-dev-framework

dia-migration

Migrates existing DIA v1/v2 repos to current conventions: detects state, strips status duplicates, renames IDs (FEATURE-NNNN→FEAT-EE-FF), flattens analysis/, regenerates BACKLOG.md, updates references, runs consistency check. Idempotent.

digital-innovation-agents

project-migrate

Migrates existing projects to AgenticDev structure using AI analysis to discover, categorize docs, generate frontmatter, update links, and preserve git history. For brownfield projects with ad-hoc documentation.

2 files

bodangren-git-workflow

Stats

Stars18

Forks3

Last CommitApr 24, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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.

CJS-only: from-gsd2 is not on the gsd-sdk query registry; call gsd-tools.cjs as shown below (see docs/CLI-TOOLS.md).

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.
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 "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" from-gsd2
```
Use --force if .planning/ already exists and the user has confirmed overwrite.
Report the result — show the filesWritten count, planningDir path, and the preview summary.

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