agentskills.codes
GS

gsd-from-gsd2

by bobby3car-ossPlanningSource

Imports projects from GSD-2 hierarchy back to GSD-1 planning formats.

Project ManagementAutomation

Install

mkdir -p .claude/skills/gsd-from-gsd2 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15277" && unzip -o skill.zip -d .claude/skills/gsd-from-gsd2 && rm skill.zip

Installs to .claude/skills/gsd-from-gsd2

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format
65 charsno explicit “when” trigger
Intermediate

Key capabilities

  • →Reverse-migrate GSD-2 projects to GSD v1 format
  • →Map GSD-2 milestones, slices, and tasks to GSD v1 structures
  • →Preserve completion states of slices and tasks
  • →Retain research files and summaries during migration
  • →Provide a dry-run preview of the migration

How it works

The skill reverse-migrates a GSD-2 project by mapping its hierarchical structure to the GSD v1 format. It preserves completion states and provides a dry-run option before execution.

Inputs & outputs

You give it
Path to a GSD-2 (.gsd/) directory
You get back
GSD v1 (.planning/) directory with migrated project structure

When to use gsd-from-gsd2

  • →Migrate GSD-2 to GSD-1
  • →Restore roadmap structure
  • →Import project research

About this skill

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

<process>

  1. Locate the .gsd/ directory — check the current working directory (or --path argument):

    node ".github/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:

    node ".github/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>

When not to use it

  • →When migrating from GSD v1 to GSD-2
  • →When the project is not in GSD-2 format
  • →When the user does not want to overwrite an existing .planning/ directory

Limitations

  • →Cannot migrate GSD-2 cost/token ledger
  • →Cannot migrate GSD-2 database state
  • →Cannot migrate GSD-2 VS Code extension state

How it compares

This skill specifically handles the reverse migration of GSD project formats, translating specific hierarchical elements and preserving states, which is distinct from general file conversion.

Compared to similar skills

gsd-from-gsd2 side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
gsd-from-gsd2 (this skill)04moReviewIntermediate
trello413moReviewBeginner
executing-plans63moNo flagsIntermediate
github-project-management46moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

trello

openclaw

Manage Trello boards, lists, and cards via the Trello REST API.

41205

executing-plans

obra

Use when you have a written implementation plan to execute in a separate session with review checkpoints

643

github-project-management

ruvnet

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

427

project-clickup

incidentfox

ClickUp project management integration for incident tracking and task management

320

coo-advisor

alirezarezvani

Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.

613

tlc-spec-driven

tech-leads-club

Project and feature planning with 4 phases - Specify, Design, Tasks, Implement+Validate. Creates atomic tasks with verification criteria and maintains persistent memory across sessions. Stack-agnostic. Use when: (1) Starting new projects (initialize vision, goals, roadmap), (2) Working with existing codebases (map stack, architecture, conventions), (3) Planning features (requirements, design, task breakdown), (4) Implementing with verification, (5) Tracking decisions/blockers across sessions, (6) Pausing/resuming work. Triggers on "initialize project", "map codebase", "specify feature", "design", "tasks", "implement", "pause work", "resume work".

77

Search skills

Search the agent skills registry