ultra-planlisted

# ultra-plan — Phase 3.3 Transform validated `.ultra/specs/` into an executable task plan. **state.db is the authority** (D32): every new task is created via MCP `task.create`; the projector regenerates `.ultra/tasks/tasks.json` and context-md frontmatter automatically. Context-md bodies are written by this skill (not projector). ## Authority failure boundary Before planning, call a state-backed MCP tool. If the MCP server is missing, unreachable, or returns any authority error, stop before creating tasks. In particular, `LEGACY_STATE_MIGRATION_REQUIRED` means the project still has a non-empty v4.4 projection; tell the user to run: ```bash ultra-tools migrate --from=4.4 --to=4.5 --source-dir <project-root> ``` Never read or write `.ultra/tasks/tasks.json` as a fallback. It is a generated projection, not an alternate task store. There is no task-mutation CLI fallback. ## Prerequisites - `/ultra-research` completed — specs must be 100% (no `[NEEDS CLARIFICATION]`) - `.ultra/specs/product.md` + `.ultra/specs/architecture.md` exist - `.ultra/specs/research-distillate.md` preferred when present (token-efficient) ## Workflow ### Workflow activation At entry, write `.ultra/workflow-state.json` with `{"command":"ultra-plan","task_id":"plan","step":"0","status":"active","ts":"<ISO8601>"}`. This activates the workflow-only hooks. Mark it terminal only after the MCP task writes and verification complete. ### Input Mode Selection (BEFORE Step 0) Two entry points lead into the