migrate-to-gsflisted

# Migrate to Creative GeekStack Flow ## When to use this skill Invoke this skill when: - A project has ad-hoc AI infrastructure (any of `.taskRef/`, `ai-mem/`, hand-written `CLAUDE.md`, `AGENTS.md`, `.github/copilot-instructions.md`, `.github/instructions/`, or similar) that overlaps with what `.tcgstackflow/` would provide. - The user wants a clean cutover rather than long coexistence (coexistence becomes permanent duplication, per ADR 0004). - You have ≥2 hours to commit to the full lifecycle including the post-migration validation sessions before decommission. **Do not use this skill** for greenfield projects — those just run `node init.js .` once. Migration is only relevant when there's prior AI infrastructure to *replace*. ## Instructions You are operating as **Planner** first (drafting the migration task), then **Coder** (executing it), then **Reviewer** (validating each phase), then **Ingester** (Phase 3 wiki work). Use the right profile at each stage; don't shortcut role discipline because the work is "infrastructural." ### High-level shape ``` Phase 1 — Init + adapters ↓ Phase 2 — Tasks migration ↓ Phase 3 — Wiki ingestion (log-first, gated new pages) ↓ Cross-cutting — Global tech-skill migration ↓ Phase 4 — Decommission (CRITICAL: requires recorded approval) ``` ### Procedure #### Pre-flight (Planner role) 0. **Detect workspace kind.** Scan top-level directories for project signal files (`package.json`, `*.csproj`/`*.sln`, `Pulumi.yaml`, `Cargo.to