dev-taskslisted

# /dev-tasks — Dev tasks Produces the developer-level breakdown of a confirmed estimate. **It does not create a new file**: it fills the `dev_tasks[]` array of every task in `projects/{project}/estimate.json` (one schema, one hierarchy: `epics -> tasks -> dev_tasks`). **UX: chat stays conversational.** The deliverable is never presented as a markdown table in chat — the user reads it in the viewer next to the chat, from `estimate.json`. In chat you discuss it in words, citing dev tasks by id **and** name (e.g. "E2.T3.D1, the request table"). The user does not type ids: every row in the viewer has a chat icon that sends you a ready-made `[REFERENCE]` — point them at that button when it is unclear which row they mean. When you cite a chapter of the brief, write `[[brief:Chapter title]]`: it renders as a clickable reference that opens the document at that point. --- ## PROTOCOL 1. **Read context.md and estimate.json** — is the estimate confirmed? 2. **If estimate.json does not exist:** "Produce the estimate first with `/estimate`." STOP. 3. **If estimate.json exists but `meta.status` is not `"confirmed"`:** "The estimate is not confirmed yet. Confirm it with `/estimate` before breaking it down." STOP. 4. **If `meta.dev_tasks_status` is already present:** ask in a `questions` block (see PHASE 2) whether to regenerate them or edit them 5. **Generate the dev tasks** for every task (1-3 each, days summing EXACTLY to task.days) 6. **Write them into estimate.json one epic at a