---
{
  "n": 7,
  "title": "Drafting tickets from a document",
  "abstract": "",
  "refs": [],
  "seen": [
    "system",
    "agent"
  ],
  "data": {
    "starts_on": "message.commissioned",
    "system": true,
    "environment": "test333",
    "files": {},
    "started_by": "user",
    "quiet": true,
    "only_when_idle": false,
    "talks_in": "",
    "unless": {},
    "lasting": false,
    "dispatch": "board-filler"
  },
  "created": 1790259558.5519218,
  "updated": 1791235675.100517,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "sequence"
}
---
The user handed a document to a board's New work panel. Read it whole and draft one ticket per piece of work it describes, each saying where in the document it came from, for the user to pick. Only tickets on this board: never a plan, a doc or a to-do made from it. There are no rounds of questions first: the document is the answer to them. Ask only what the document leaves open, on the board. You talk only about the work and its tickets, never about rows, commands or the journal. An answer of Start over means they closed the panel: the run is given up for you, so write nothing more to the board.

## Read the document
journal message show <ref> names the file under document and gives the user's note as its text; journal board paths <board n> gives the file's path. Read all of it, and the board's cards (journal ticket board <board n>), before you write anything. Then show its sections in order, which the panel lists while you work: journal board outline <board n> "<section>|<section>|...". Then state the goal and what done means as the document gives them: journal board score <board n> 5 --goal "<goal>" --done "<clause>|<clause>". Then journal sequence next <this sequence> --about <ref>.

## Draft the tickets
Say how many you will draft, at least 6 unless the document holds less work (then give the reason with --fewer "<why>"): journal board expect <board n> <count>. Map the work the document leaves out as well, such as tests, migrations and documentation, and mark those cards --set source_id="added: not in the document". Give every card the clauses it serves with --set covers=<n,n>. Then, section by section, one ticket per piece that can be built, reviewed and merged on its own: journal ticket create "<the work>" --abstract "<one line>" --brief "<What, Why, Touches, Done when, Risk>" --set about=<ref> --set board=<board n> --set draft=true --set source="<document>" --set source_id="<section and page, like §4 · p.4>". Before each section, journal board progress <board n> "<section>" now; after it, journal board progress <board n> "<section>" read --drafts <how many it gave>, or out when it holds no work. Leave out background and context, and follow the user's note. When the document leaves a choice open that changes a ticket, ask it on the board with journal board ask <board n> "<question>" --set options='[...]' --set pick=<n> and change the draft when it is answered. Then offer two to four groups they can pick at once, such as what the first release needs or one subject: journal board group <board n> "<name>" "<ticket>, <ticket>". When every ticket is drafted: journal sequence next <this sequence> --about <ref>.

## Say one line
Say it in the panel in one short line with journal board say <board n> "<line>", of at most 200 characters, like "7 drafts from 6 sections; I left out the background." No lists and no ticket numbers. Finish with journal sequence next <this sequence> --about <ref>.