source-command-gsd-from-gsd2
Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format
Best use case
source-command-gsd-from-gsd2 is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format
Teams using source-command-gsd-from-gsd2 should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/source-command-gsd-from-gsd2/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How source-command-gsd-from-gsd2 Compares
| Feature / Agent | source-command-gsd-from-gsd2 | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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>
Related Skills
llm-wiki-source-extraction-coverage
Doc-type-aware extraction contract for llm-wiki source ingestion with measurable coverage and source-anchored traceability. Use when (1) ingesting a PDF, DOCX, XLSX, PPTX, HTML, or scanned-image source into a wiki `sources/` page, (2) computing the pre-extraction estimate (what fraction of the source we expect to recover) and post-extraction yield (what fraction we actually recovered), (3) anchoring wiki claims back to specific page / paragraph / cell / slide positions in the source so a reviewer can re-verify or revise against the actual document, (4) deciding whether OCR fallback or manual transcription is needed. Codifies workspace-hub's existing OCR fallback chain and python-docx / openpyxl / trafilatura patterns into a format-specific routing table. Companion to research/llm-wiki-page-shape-contract (Rule 7 input-layer pages) and research/llm-wiki — this skill is the defense against silent extraction failure.
worldenergydata-source-readiness
Route agents to the canonical worldenergydata source-readiness skill and summary script. Use when asked for worldenergydata data completeness, data locations, latest known data dates, scheduler freshness, source-readiness status, or acceptance-criteria inputs across the repo ecosystem.
multi-source-tax-document-reconciliation
Verify generated tax forms against source documents by line-by-line comparison, not just totals
source-command-learn-extended
Extract learnings from the current session and convert them to actionable repo content. Phase 4 of #1760.
source-command-gsd-workstreams
Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
source-command-gsd-review-backlog
Review and promote backlog items to active milestone
source-command-gsd-join-discord
Join the GSD Discord community
source-command-compound-extended
Run cross-agent memory bridge. Sync learnings between machine agents, update shared knowledge. Phase 5 of #1760.
github-issue-label-audit-and-command-bundles
Safely turn drafted issue bodies into reusable gh issue create commands by auditing repo labels, exact duplicates, and auth first.
knowledge-source-recon
Reconnaissance pattern to inventory all knowledge sources across the workspace-hub ecosystem's existing intelligence infrastructure. Maps raw sources for LLM Wiki ingestion planning. Leverages pre-built registries and indexes rather than re-scanning directories.
source-management
Configure and query MCP data sources for enterprise search. Use when checking which sources (chat, email, cloud storage, CRM, knowledge base) are connected, connecting new ones, or tuning query priority and rate limits.
repo-cleanup-progress-tracking-commands
Sub-skill of repo-cleanup: Progress Tracking Commands (+1).