dispatch-task-createlisted

Wrap `mcp__vantage-peers__create_task` so every dispatched task ships with the IRP doctrine blocks (VERIFICATION, TESTS, IRP) that `enforce-task-quality.py` requires, the delegation triplet (`subagent_type` + `run_in_background` + `model`) that `enforce-pi-task-doctrine.py` requires for batch ops, the `// allow-no-notify` marker that `enforce-create-task-notify-followup.py` requires for multi-task dispatches to the same assignee, plus the drain-notify-queue check (Step 1.3) that prevents cross-assignee dispatch blocks, plus the right assignee, priority, mission link, and dependency wiring. **Canonical source**: VantageRegistry (`get_skill_content name=dispatch-task-create`). The local `.claude/skills/dispatch-task-create/SKILL.md` in each workspace MUST be a byte-exact mirror of the VR canonical content. Fetch from VR — do not edit locally. ## WORKFLOW **Step 0 — Pre-flight (typed-params recipe, Day 113)** Before the first `create_task` of a session, load the schema: ``` ToolSearch query="select:mcp__vantage-peers__create_task,mcp__vantage-peers__send_message" ``` Read the required params: `title`, `assignedTo`, `priority`, `createdBy`, `description`. Optional: `missionId`, `dependsOn` (array of strings, NEVER bare token). **Step 1 — Gather context** 1. Parse user intent: extract the assignee (sigma, eta, alpha, lambda, tau, phi, omega, zeta, …), the work, and any cited mission / parent task / PR / issue. 2. If the user named a mission, resolve its `missionId` via `li