tcgflow-migratelisted

# `/tcgflow-migrate` — migrate existing AI infrastructure ## When to use The user typed `/tcgflow-migrate` or said *"migrate this project to geekstackflow"*, *"move from .taskRef to .tcgstackflow"*, *"cutover the AI infra"*. The current directory has prior AI scaffolding that needs to be replaced. ## What to do You are operating the `migrate-to-gsf` skill against the current directory. Follow its full procedure; the high-level pattern is: 1. **Pre-flight (Planner role).** Inventory existing AI infrastructure. Classify each item: migrate / fold-into-agent-profile / unique-skill / archive-to-bak / discard. Distinguish actually-active tasks from stale carry-overs. Detect workspace kind (single vs multi-project). 2. **Commit pending git work** as a pre-migration snapshot if the user agrees — gives clean rollback. 3. **Backup the old AI infra to `.bak` siblings** (Phase 1): ```bash mv .taskRef .taskRef.bak mv ai-mem ai-mem.bak mv CLAUDE.md CLAUDE.md.bak mv AGENTS.md AGENTS.md.bak mv .github/copilot-instructions.md .github/copilot-instructions.md.bak mv .github/instructions .github/instructions.bak ``` Adjust paths to match what the project actually has (.taskRef/ vs .tasks/, docs/ vs ai-mem/, etc.). 4. **Run `geekstackflow init --migrate-from . .`** — installs the workspace AND collects the old artifacts into `.tcgstackflow/migration-notes/` for manual review. 5. **Adopt Planner role** (`agents/planner.md`) and use `plan-task` to write a `TASK d