migrate-plans

Migrate legacy .ai plan layouts to slug-based directories with non-destructive moves.

59|3|Updated Jan 23, 2020

Search Tags:#automation #filesystem #legacy #migrate #project-structure #plan-management

Ready to run

npx skills add https://github.com/michaeldyrynda/dotfiles --skill migrate-plans

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-plans
Source: https://github.com/michaeldyrynda/dotfiles/tree/main/agents/skills/migrate-plans
Command: npx skills add https://github.com/michaeldyrynda/dotfiles --skill migrate-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy .ai directory layouts are flat and hard to scale; migrating to a slug-based plans directory improves organization and future maintenance.

Core Features & Use Cases

Discover legacy plan files and derive destination slugs for migration
Create the new directory structure under .ai/plans/{slug} and move plan/spec/learnings/tasks accordingly
Guardrails and prompts ensure slug confirmation and non-destructive moves, with a final report of changes

Quick Start

Confirm the slug for each plan and run the migrate-plans skill to reorganize the .ai directory.

Frequently Asked Questions about migrate-plans

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

FAQPage Schema

How do I migrate legacy .ai plan files to a slug-based directory structure?▼

To migrate legacy .ai plan files, you can automate the process of discovering plan.md files and tasks folders, deriving destination slugs, and moving them into a structured .ai/plans/{slug} layout. This ensures safe reorganization and improved future maintenance.

What is a slug-based structure for project plans and why is it needed?▼

A slug-based structure organizes flat legacy plan layouts into dedicated directories under .ai/plans/{slug}. This structure is needed because flat directory layouts are hard to scale, and migrating them improves overall project organization and future maintenance.

Can I safely reorganize .ai directories without losing existing plan or task files?▼

Yes, you can safely reorganize .ai directories using non-destructive moves. The migration process creates new directories, moves plan, spec, learnings, and tasks files accordingly, and cleans up empty folders while prompting for slug confirmation to prevent data loss.

How do I automate moving legacy tasks folders into a new plans directory layout?▼

You can automate moving legacy tasks folders by running a migration process that discovers existing plan files, derives target slugs, creates the new directory structure, and executes non-destructive file moves before cleaning up empty directories and reporting changes.

Does the plan migration process require manual confirmation before moving files?▼

Yes, the plan migration process requires manual slug confirmation before moving files. Guardrails and prompts ensure you confirm the derived slug for each plan, guaranteeing non-destructive moves and providing a final report of all changes made.