Migrate Subfeatures

Use this skill when a repository still contains legacy planning artifacts from the old change-based workflow and those artifacts need to be converted into the current durable subfeatures/ model.

Responsibilities

1. Resolve one feature or the full planning tree.
2. Detect legacy changes/<change-id>/ packets.
3. Convert legacy .feature-change-meta.json into .subfeature-meta.json.
4. Create .planning-meta.json for migrated subfeatures.
5. Rebuild feature-local subfeature registries and resync the planning registry.

Preferred Input

• a feature slug, folder name, or path when migrating one feature
• or --all for a repo-wide migration
• optional --dry-run before modifying planning files