migratelisted

# /mneme:migrate — Turn an external spec into workflow phase files, end at the map The door for EXTERNALLY-authored specs. It takes a path to a spec, drives the engine's `workflow_migrate` tool through validate → apply-if-clean in ONE pass, and ends by rendering the GRAPH-MAP of the migrated phases — it never runs them. The split by spec origin: a spec BORN from `/mneme:plan` is migrated by plan's own finale (fail-fast, hot context); a spec BROUGHT from outside comes through this skill. Both doors drive the SAME engine tool, `workflow_migrate` — this skill adds no conversion logic of its own. ## Arguments `/mneme:migrate <path-to-spec>` — the spec file to migrate (e.g. `docs/SPEC-D9-SOMETHING.md`). No argument → ask for the spec path (one line), never guess one. If the path does not exist or is not readable, say so and stop. ## Permissions (VIOLATION = ABORT) - Read: YES — to confirm the spec exists (and quote a line when explaining an error). - `mcp__plugin_mneme_memory__workflow_migrate`: YES — the ONLY engine tool this skill drives. The TOOL writes the phase files; the skill itself writes nothing. - Edit / Write / Bash / Grep: FORBIDDEN — no hand-authored phase files, no hand-fixes of conflicts, no directory surgery. Conflict resolution is the USER's move, guided by the options below. - `workflow_start` / `workflow_step` / `/mneme:dev`: FORBIDDEN — the skill ENDS at the map; running the phases is the user's next move. - `recall` / `remember` / any memory tool: