gsd-from-gsd2

Converts GSD-2 projects to GSD v1 structure via gsd-tools.cjs.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-from-gsd2-poom5741
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-from-gsd2
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-from-gsd2
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-from-gsd2-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reverse-migrate a GSD-2 project (.gsd/ directory) back to GSD v1 (.planning/) format by mapping Milestone → Slice → Task to ROADMAP.md checklists and phase lists while preserving completion state, research files, and summaries.

Core Features & Use Cases

  • End-to-end migration from GSD-2 to GSD v1, aligning hierarchy and preserved metadata.
  • State preservation of completed milestones, slices, and tasks, plus associated notes and research files.
  • Non-destructive tooling using gsd-tools.cjs with dry-run capability and optional force overwrite for existing planning directories.

Quick Start

Run the from-gsd2 migration on your repository to convert a GSD-2 project into its GSD v1 planning structure.

Frequently Asked Questions about gsd-from-gsd2

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a GSD-2 project back to GSD v1 format?

To convert a GSD-2 project back to GSD v1, run the from-gsd2 migration to map the .gsd/ directory structure into .planning/ format, translating Milestone, Slice, and Task hierarchies into ROADMAP.md checklists and phase lists while preserving completion states.

Does the GSD-2 to GSD v1 migration preserve task completion states?

Yes, the migration preserves the completion state of milestones, slices, and tasks, while also retaining associated research files and summaries during the mapping to the GSD v1 .planning/ structure.

Can I preview the GSD-2 reverse migration before writing files?

Yes, you can preview the reverse migration by using the dry-run capability in the gsd-tools.cjs CLI, allowing you to verify the Milestone to ROADMAP.md mapping before writing files to the .planning/ directory.

How do I overwrite an existing .planning directory during GSD migration?

To overwrite an existing .planning directory during GSD migration, use the --force option with the gsd-tools.cjs CLI; otherwise, the tool writes to the existing directory without overwriting current data.

Do I need the gsd-tools.cjs CLI to reverse migrate GSD-2 projects?

Yes, the gsd-tools.cjs CLI is required to perform the reverse migration from GSD-2 to GSD v1, as it handles the mapping logic and supports the --path option to target specific project repositories.

What is the best way to map GSD-2 milestones to GSD v1 ROADMAP checklists?

The best way to map GSD-2 milestones to GSD v1 ROADMAP checklists is using an automated migration tool that translates the Milestone, Slice, and Task hierarchy directly into the phase lists and checklists required by the .planning/ format.