dispatching-research-tasklisted

# Dispatching a Research Task **Render before asking.** Before any AskUserQuestion, render the decision context as assistant chat text. Content that exists only in a Read result, a subagent/Agent return, or the question/option strings **does not count as rendered** (the UI shows a compact card) — restate it in chat first. A `kind: research` task answers a question. Its deliverable is a markdown findings doc, not code. The subagent reads (codebase, web, docs), reasons, and writes a single output file. Wrong dispatch → silent-pass bug: feature builders have no Red step for a research-shaped task and exit clean on an empty tree, satisfying the "Before Exiting" gate trivially. Route here. ## When to Invoke `/ship-execute` calls this skill when a task's frontmatter has `kind: research`. Other entry points: - `/ship-discuss` may invoke this for an inline technical investigation during feature shaping ("which JWT library should we use?"). - `/ship-sprint` may invoke this during planning when a feature can't be specced without a design tradeoff analysis. Per the action items, the routing decision (`kind: feature` vs `operational` vs `research`) lives in the calling command skill. This skill assumes the routing already chose research. ## Inputs - `task_id` — e.g., `R-013` (research tasks conventionally use `R-` prefix, but any ID works). - `task_file_path` — absolute path under `<SHIPYARD_DATA>/spec/tasks/`. - `parent_feature_path` — absolute path or null. - `data_dir` — liter