migrate-plans

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.

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.

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.

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.

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.