migrate-speclisted

# Migrate Spec Transform existing GSD, spec-kit, or BMAD planning artifacts into the bigpowers `specs/` model. No code is written — the output is a set of bigpowers-format spec files the user can use immediately. ## Quick start 1. Run this skill from the root of the project being migrated (not the bigpowers repo itself). 2. The skill auto-detects the source framework and presents its findings before transforming anything. 3. All output goes to `specs/` at the project root. ## Red flags — stop and ask Before proceeding, check for these rationalization traps: - **Partial artifact set** — only one fingerprint file found (e.g. just `spec.md` with no `plan.md`). Don't assume it's a complete project. Ask: "I found only X — is this the full set of your spec artifacts?" - **Wrong trigger** — user said "migrate my code" or "migrate the database", not "migrate my specs". Confirm before running. - **Stale source** — source artifacts have commit dates older than 6 months with no recent activity. Flag: "These specs appear inactive since <date>. Are they still the source of truth?" - **Active divergence** — source `state.yaml` or `sprint-status.yaml` shows in-progress work. Flag: "There is active work in flight. Migrating now may lose in-progress context. Proceed?" If any red flag fires: surface it, wait for explicit user confirmation before continuing. ## Process ### Step 1 — Detect the source framework Scan for the fingerprints below. Stop at first match; if multiple match, l