plan-migrate

Name: plan-migrate
Availability: InStock
Author: honigbart

Migrate legacy .ai singleton layouts to namespaced plan directories.

1|Updated Apr 6, 2026

Search Tags:#migration #project-management #slug-generation #safety-checks #plan-layout #ai-directory #artifact-migration

Ready to run

npx skills add https://github.com/Honigbart/honeyflow --skill plan-migrate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-migrate
Source: https://github.com/Honigbart/honeyflow/tree/main/plan-migrate
Command: npx skills add https://github.com/Honigbart/honeyflow --skill plan-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates an existing project's .ai directory from the legacy singleton layout to the namespaced plan layout.

Core Features & Use Cases

Detects legacy .ai structures and advises migration.
Creates .ai/plans/<slug>/ directories and moves relevant artifacts (final_plan.md, execution_state.md, session_log.md, claude_brainstorm.md, codex_critique.md, evolution_plan.md, review.md).
Generates a centralized plans.md index with status mapping and a one-line description.
Guides step-by-step migration with safety checks and user confirmations.

Quick Start

Initiate migration by confirming the detected legacy layout when prompted, then follow the tool's step-by-step prompts to relocate artifacts.

Frequently Asked Questions about plan-migrate

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

FAQPage Schema

How do I migrate legacy .ai directory structures to a namespaced plan layout?▼

To migrate legacy .ai directory structures, the tool detects existing singleton artifacts like final_plan.md, generates a slug, and safely relocates them into a .ai/plans/<slug>/ directory with a centralized plans.md index.

When do I need to migrate my .ai directory from the singleton layout?▼

You need to migrate your .ai directory from the singleton layout when your project contains .ai/final_plan.md without a corresponding .ai/plans.md file, or when a pipeline detects the legacy layout and prompts a migration.

What is the best way to safely relocate in-progress AI artifacts during a layout migration?▼

The best way to safely relocate in-progress artifacts like execution_state.md and session_log.md is to use guided step-by-step prompts with built-in safety checks and user confirmations before moving files into the namespaced layout.

What specific files are moved when migrating to the namespaced plan layout?▼

Migrating to the namespaced plan layout moves root and in-progress artifacts including final_plan.md, execution_state.md, session_log.md, claude_brainstorm.md, codex_critique.md, evolution_plan.md, and review.md into the new directory structure.

Does the migration process generate an index for the new namespaced plan layout?▼

Yes, the migration process generates a centralized plans.md index file that maps the status of each relocated artifact and includes a one-line description for the newly created namespaced plan directories.

Can I automate artifact migration without manually confirming each step?▼

Artifact migration requires user confirmations at each step to ensure safety, meaning you cannot fully automate the process without manual approval when relocating legacy files into the namespaced layout.