How do I install the Source Command Gsd From Gsd2 skill?

Run npx skillmds@latest add vamseeachanta/source-command-gsd-from-gsd2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Source Command Gsd From Gsd2 skill do?

Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format It is listed under Coding & Dev Tools on SkillMD.

Is Source Command Gsd From Gsd2 safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Source Command Gsd From Gsd2?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Source Command Gsd From Gsd2 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Source Command Gsd From Gsd2?

vamseeachanta (@vamseeachanta) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Source Command Gsd From Gsd2 by vamseeachanta

Name: Source Command Gsd From Gsd2
Author: vamseeachanta

File contents

source-command-gsd-from-gsd2

Use this skill when the user asks to run the migrated source command gsd-from-gsd2.

Command Template

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 "/mnt/local-analysis/workspace-hub/.Codex/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 "/mnt/local-analysis/workspace-hub/.Codex/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.

---name: source-command-gsd-from-gsd2description: Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format---# source-command-gsd-from-gsd2Use this skill when the user asks to run the migrated source command `gsd-from-gsd2`.## Command Template<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.**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><process>1. **Locate the .gsd/ directory** — check the current working directory (or `--path` argument): ```bash node "/mnt/local-analysis/workspace-hub/.Codex/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: ```bash node "/mnt/local-analysis/workspace-hub/.Codex/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.</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>

Frequently asked questions

Source Command Gsd From Gsd2