migrate

Restructure legacy .project/ or .goodplan/ directories into epics, slices, and quests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ian97531/goodplan --skill migrate-ian97531
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/ian97531/goodplan/tree/main/skills/migrate
Command: npx skills add https://github.com/ian97531/goodplan --skill migrate-ian97531

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate converts a legacy project directory into a CLI-managed state by restructuring .project/ or .goodplan/ into epics, slices, and quests while preserving existing artifacts during migration.

Core Features & Use Cases

  • Automatic detection of legacy formats (.project/ and .goodplan/).
  • Interactive multi-round Q&A to inventory epics, slices, and quests and perform artifact copying.
  • Safe migration with pre-flight checks, backups, and validation.

Quick Start

Run gp migrate to begin the interactive migration workflow for converting a legacy project to CLI-managed state.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I migrate legacy project directories to a CLI-managed state?

To migrate legacy project directories to a CLI-managed state, run the gp migrate command to initiate an interactive workflow that restructures existing .project/ or .goodplan/ folders into epics, slices, and quests while preserving artifacts.

What is the process for converting old .goodplan folders into epics and slices?

Converting old .goodplan folders into epics and slices involves a guided multi-round Q&A workflow that inventories existing project structures, detects legacy formats, and builds a new validated state with backups.

Does the migration workflow require any specific CLI tools or dependencies?

Yes, the migration workflow requires the gp CLI tool to execute pre-flight checks, perform guided artifact copying, and output a finalized project.json with an organized directory structure suitable for command-line management.

Can I preserve existing project artifacts when restructuring to a CLI-managed state?

Yes, you can preserve existing project artifacts when restructuring to a CLI-managed state because the migration process includes pre-flight checks, validation, and backups to ensure original files are safely maintained during the conversion.

What happens if the legacy project format detection fails during migration?

If legacy project format detection fails during migration, the process applies error handling and pre-flight checks to safely halt operations, ensuring your legacy directory structure remains protected with backups before any changes are committed.

Is there a best way to restructure legacy project state into epics, slices, and quests?

The best way to restructure legacy project state into epics, slices, and quests is using a guided multi-round Q&A workflow that automatically detects old formats and validates the new project.json output during the conversion.