Skip to content
Back to skills

Source Command Gsd From Gsd2

ASecurity

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

  • 17 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 9, 2026
businessbashnodedatabase

Works with

  • cli

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add vamseeachanta/workspace-hub --skill source-command-gsd-from-gsd2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Source Command Gsd From Gsd2?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Source Command Gsd From Gsd2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vamseeachanta-source-command-gsd-from-gsd2/badge)](https://www.skillsdirectory.com/skills/vamseeachanta-source-command-gsd-from-gsd2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "source-command-gsd-from-gsd2"
description: "Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format"
---

# source-command-gsd-from-gsd2

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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.