What problem does it solve?
When migrating legacy applications, large source files are often tracked as single work items, leading to missing functionality even if the code compiles, because the work wasn't broken down into granular, trackable features with clear verification steps.
Core Features & Use Cases
- Granular Feature Decomposition: Breaks down source application files into individual features sized for 30 minutes to 4 hours of work, with explicit source file line references and dependency mapping.
- Auto-Detection of Completed Work: Automatically runs verification criteria against existing target files to mark already migrated features as complete, avoiding redundant work.
- Prioritized Work Queue Generation: Produces a sorted list of remaining tasks ordered by priority and dependencies, so migration teams always know what to work on next.
- Use Case: A team migrating a legacy Slack mood tracker bot can use this skill to break down components like Slash commands, Supabase integration, and daily check-in triggers into individual trackable tasks, ensuring no functionality is missed during the migration.
Quick Start
Use the migrate-decompose skill to break down your migration manifest for the mood-tracker Slack bot into individual, trackable feature tasks with clear verification criteria.
