migration-planning

Plan One-UI migrations with tool references and checklists.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Michael0520/milo-claudekit --skill migration-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-planning
Source: https://github.com/Michael0520/milo-claudekit/tree/main/plugins/one-ui-migration/skills/migration-planning
Command: npx skills add https://github.com/Michael0520/milo-claudekit --skill migration-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the planning of One-UI migrations by integrating with the superpowers workflow and ensuring all necessary tool references are considered, leading to more robust and compliant migration plans.

Core Features & Use Cases

  • Tool Mapping: Automatically identifies required tools based on legacy component types.
  • Workflow Integration: Seamlessly integrates with superpowers:brainstorming and superpowers:writing-plans.
  • Checklist Generation: Provides detailed checklists for various tools to ensure adherence to standards.
  • Use Case: Before starting a large feature migration, use this Skill to generate a comprehensive plan that includes all necessary tool references and verification steps, ensuring consistency and reducing errors.

Quick Start

Use the migration-planning skill to brainstorm the tools needed for migrating a legacy form component.

Frequently Asked Questions about migration-planning

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

FAQPage Schema
How do I plan a One-UI migration for legacy components?

Plan a One-UI migration by identifying necessary tools for legacy forms, tables, and dialogs, then generating detailed implementation checklists. This ensures structured planning across domain, feature, and UI layers for robust project execution.

What is the best way to map tools for a legacy code migration?

Mapping tools for a legacy code migration involves automatically identifying required tooling based on legacy component types. This process ensures adherence to code standards by providing detailed checklists for implementation and verification.

Can I use this migration planning workflow with the superpowers brainstorming process?

Yes, you can use this migration planning workflow with the superpowers brainstorming process. It seamlessly integrates with superpowers:brainstorming and superpowers:writing-plans to generate comprehensive plans that include necessary tool references.

Does the One-UI migration planning process provide verification steps?

Yes, the One-UI migration planning process provides verification steps. It generates detailed checklists for various tools to ensure adherence to code standards, reducing errors and ensuring consistency during implementation.

When do I need to generate a checklist for a UI layer migration?

You need to generate a checklist for a UI layer migration before starting a large feature migration. This ensures all necessary tool references and verification steps are considered, leading to compliant migration plans.