nav-pilot

# Navigator → Pilot Dispatch Skill Hand a finished Navigator task doc off to Pilot by creating the `pilot`-labeled GitHub issue Pilot polls, then record the issue back into the doc. **This skill does NOT validate the doc.** Spec checking is Pilot's job (its `spec_validator`). nav-pilot only resolves the doc, creates the labeled issue, and records the result. It consumes what `nav-task` authored — it does not author or archive docs itself. ## When to Invoke Invoke when the user says: - "Dispatch TASK-XX to Pilot" - "Hand this off to Pilot" / "send to Pilot" - "Queue TASK-XX for Pilot" / "create the Pilot issue" **DO NOT invoke** when: - User is authoring/archiving a task doc (that's `nav-task`) - User wants Pilot worker status (out of scope — this skill is one-way) - No task doc exists yet (tell them to create one with `nav-task` first) ## Execution Steps ### Step 1: Resolve the Target Task Doc - **Explicit ID** ("TASK-07"): use `.agent/tasks/TASK-07-*.md`. - **No ID**: pick the active/in-progress task. If ambiguous, list candidates (`ls .agent/tasks/*.md`) and ask which one. - If the file does not exist, stop and tell the user to author it first. Read the doc and extract: - **Title** = the first H1 (`# TASK-XX: <name>`), stripped of the `TASK-XX:` prefix if present (or keep the full H1 — match what Pilot expects). - **Body file path** = the doc itself (passed via `--body-file`, never inlined). ### Step 2: Load Pilot Config Read `pilot` from `.agent/.nav-config....