hatch3r-migration

# Migration Workflow ## Quick Start ``` Task Progress: - [ ] Step 0: Detect ambiguity (P8 B1) - [ ] Step 1: Assess migration scope - [ ] Step 2: Analyze breaking changes - [ ] Step 3: Create migration plan - [ ] Step 4: Execute migration phases - [ ] Step 5: Validate and verify - [ ] Step 6: Document and clean up ``` ## Step 0 — Detect Ambiguity (P8 B1) Before any work, scan the invocation for unresolved questions in scope, intent, acceptance criteria, target environment, or irreversibility. If any are found, ask the user via the platform-native question tool per `agents/shared/user-question-protocol.md`. Do not proceed under silent assumption. Default path, not an exception. Triggers for THIS skill: target version pinned, allowed downtime window, irreversible operations (schema drops, data deletes), rollback acceptable as cold restore vs hot revert, and consumer compatibility window (single PR vs phased). ## Fan-out Discipline (P8 B2) Fan-out scales with task size; token cost never justifies serializing independent work (`rules/hatch3r-fan-out-discipline.md` P8 B2; `agents/shared/efficiency-patterns.md`). Emit `sub_agents_spawned: { count, rationale, task_structure }` in your output. ## Step 1: Assess Migration Scope - Identify the migration type: database schema, framework version, dependency upgrade, language version, or infrastructure change. - Inventory all affected files, modules, and services. - Check for transitive dependency impacts — upgrading one package ma...