migrate-legacylisted

# Migrate a legacy application — the seven-phase pipeline Upgrade a legacy application completely, verifiably, easily, and fast. You are the orchestrator: drive the phases **in order**, never advancing past a red gate. Throughout this skill and its references, **`<kit>`** is the plugin root — resolve it as `<skill-dir>/../..`, where `<skill-dir>` is this skill's base directory (given when the skill loads). Every kit script and template path (`<kit>/scripts/…`, `<kit>/templates/…`) resolves from there — never from the current working directory, which is the *target* repo. ## Phase 0 — Preflight (before anything else) 1. **Run `<kit>/scripts/preflight.sh`** (deterministic; a missing REQUIRED item = stop). The canonical prerequisite list — tools, MCP servers, session skills, each required or recommended, plus the `requiredBy` list where a specific skill hard-requires an entry — lives in **`<kit>/requirements.json`**: the script reads it, nothing is duplicated here. To add or remove a prerequisite, edit THAT file. Re-run with `--json` for the machine version to store in `migration/report.json`. 2. **Confirm the session capabilities** (the script cannot see the session): for every `sessionSkills` entry and every MCP in `requirements.json`, verify presence in YOUR list of skills/tools. The usage moments stay hard rules: `mcp__roseline__*` **mandatory** for any C# (otherwise stop and ask for the configuration); `context7` before phases 3/5 and before any UI; `frontend-design` **