skills.rest
adobe
adobeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

migration-prep

Plan Phase 1 migration from 1st-gen to 2nd-gen components.

1.5k|257|Updated Nov 19, 2018
Search Tags:#planning#architecture#migration#roadmap#component#api-surface#gen1-gen2
One-click install
npx skills add https://github.com/adobe/spectrum-web-components --skill migration-prep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration-prep
Source: https://github.com/adobe/spectrum-web-components/tree/main/.ai/skills/migration-prep
Command: npx skills add https://github.com/adobe/spectrum-web-components --skill migration-prep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase 1 of the 1st-gen to 2nd-gen component migration. The goal is to thoroughly understand the component and produce a written migration plan—covering API surface, breaking changes, file layout, and naming decisions—before any code is moved or refactored.

Core Features & Use Cases

  • Document current API surface and dependencies to establish baseline.
  • Define breaking changes and create a detailed migration plan and scope.
  • Use during project planning meetings to align team understanding before implementation.

Quick Start

Initiate migration prep for a component by producing a written Phase 1 plan that documents API surface, breaking changes, file layout, and naming decisions prior to any code changes.

Frequently Asked Questions about migration-prep

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

FAQPage Schema
How do I plan a 1st-gen to 2nd-gen component migration?▼

To plan a 1st-gen to 2nd-gen component migration, document the current API surface, identify breaking changes, and define file layout and naming decisions in a written plan before refactoring begins.

What is included in a Phase 1 migration plan?▼

A Phase 1 migration plan includes the defined API surface, breaking changes, file layout, naming decisions, scope, dependencies, and success criteria established before code changes occur.

When should I document API surface and breaking changes for a migration?▼

You should document API surface and breaking changes during early migration workstreams to establish a baseline and align team understanding before any code is moved or refactored.

Does migration prep help with project planning meetings for component refactoring?▼

Migration prep helps with project planning meetings by providing a written Phase 1 plan that aligns team understanding of component scope, dependencies, and naming decisions prior to implementation.

What are the limitations of starting a component migration without a written plan?▼

Starting without a written migration plan risks misaligned understanding of breaking changes, undefined API surface, and unclear naming decisions, which can cause errors during subsequent code refactoring.

Related Skills

Explore More Software Engineering Skills→
adobeadobe
1.5k

migration-setup

Scaffold SWC directory structure and stub files for export wiring.

Official
Intermediate
adobeadobe
1.5k

migration-styling

Migrate CSS to 2nd-gen structure with Spectrum 2 tokens and stylelint conformance.

Official
Intermediate
Poom5741Poom5741

gsd-list-phase-assumptions

Surface Claude's assumptions about phase-based roadmaps before planning.

Community
Intermediate
Marcus-Mok-GHMarcus-Mok-GH

breaking-change-detector

Detect breaking API, schema, and interface changes in code.

Community
Advanced