gsd-migrate

Name: gsd-migrate
Availability: InStock
Author: Tibsfox

Migrate legacy git repositories into a structured GSD workspace with planning artifacts.

69|9|Updated Jan 30, 2026

Search Tags:#planning #brownfield #migrate #project-structure #history-preservation #gsd

Ready to run

npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill gsd-migrate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-migrate
Source: https://github.com/Tibsfox/gsd-skill-creator/tree/main/examples/skills/gsd-migrate
Command: npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill gsd-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates legacy projects into a structured GSD workspace without rewriting git history, preserving commits and decisions.

Core Features & Use Cases

Detects project type and state from repository metadata.
Generates planning artifacts: PROJECT.md, ROADMAP.md, STATE.md, and a .planning/config.json.
Preserves git history; migrates structure on top of existing history.
Produces a migration plan with phased work mapping.
Supports interactive confirmation with a guided plan.

Quick Start

Run the gsd-migrate command on your repository to generate planning artifacts and a migration plan.

Frequently Asked Questions about gsd-migrate

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

FAQPage Schema

How do I migrate a legacy project to a structured workspace without rewriting git history?▼

This migration process detects your project state from repository metadata and creates a phased migration plan, allowing you to transition a brownfield codebase into a structured GSD workspace safely.

What planning artifacts are generated when migrating a brownfield codebase?▼

These artifacts capture the project type and state detected from your repository metadata, providing a phased work mapping and a guided migration plan for the existing codebase.

Can I preserve my existing git commits when applying a new project structure?▼

This allows you to maintain your full commit history and documented decisions while safely transitioning to the new phase-based artifact generation system.

What is the best way to create a phased migration plan for an existing repository?▼

This approach ensures the migration plan is tailored to your specific brownfield codebase, generating the necessary configuration and roadmap files while keeping your git history intact.

Does this migration approach work with any brownfield codebase that has git history?▼

It safely applies the structured workspace on top of your current project state, ensuring that the phase-based artifact generation and guided migration plan fit your existing setup.