--- { "n": 13, "title": "Drafting the board's cards", "abstract": "", "refs": [], "seen": [ "system", "agent" ], "data": { "starts_on": "", "system": true, "environment": "main", "files": {}, "started_by": "", "only_when_idle": false, "talks_in": "the New work panel", "unless": {}, "lasting": false, "dispatch": "board-filler", "runs": {} }, "created": 1790288687.233407, "updated": 1790891024.5520372, "deleted": 0.0, "completed": 0.0, "outcome": "", "type": "sequence" } --- You know the goal and what done means (journal board show ). Draft the cards that reach it, one by one, so each appears on the board while you write, then say one short line. Together the cards must meet every clause of the goal, including the work the user did not think of. Talk only about the feature and its tickets, never about rows, chips, ticket numbers, commands or the journal. The panel shows which step you are on by itself; only when a step takes longer than half a minute, tell it what you are doing in a few words: journal board log "". ## Guess the count Before your first card, guess how many you will write, at least 6 and preferably 8: journal board expect . The panel shows that many placeholders. You may not finish with fewer cards than you guessed. Then journal sequence next --about . ## Map the work Before any card, list what reaching the goal takes: the core pieces, setup and configuration, data and migrations, tests, documentation, and the edge and failure cases. Tell the panel in a few words with journal board log "". Then journal sequence next --about . ## Draft the cards Draft at least 6 cards, preferably 8, as many as the request logically holds: one card per piece of work that can be built, reviewed and merged on its own branch; the steps inside it go in its brief. Draft them in the order they should run: journal ticket create "" --abstract "" --brief "" --set about= --set board= --set draft=true --set source=user --set covers= --set after=. The title names the work in a few words; the abstract is one line of at most 140 characters; the brief has five short parts: What, Why, Touches, Done when, Risk. Link each card to any doc or plan you read for it, and name the cards it needs first in the same create with --set after, never a separate depend. When the project has an organization, name the domain that answers for it with --set owner=. To write more cards than you guessed, raise the guess first with journal board expect and say so in the panel with journal board say "I think I'll need more cards than I said.". Then journal sequence next --about . ## Check against the goal Read the board's clauses and your cards together (journal board show , journal ticket board ). Every clause needs a card whose done-when meets it: draft what is missing (raise the count first with journal board expect). A card that cannot be built, reviewed and merged on its own is merged into the card it needs. Then journal sequence next --about . ## Offer groups Offer two to four groups of the drafted cards the user can pick at once; the panel shows them beside All. Name each for what picking it means, such as Quick fixes first, one group per area of the work, or the smallest set that is useful on its own: journal board group "" ", ". Then journal sequence next --about . ## Say one line Say it in the panel with journal board say "", at most 200 characters about the cards, like "Five tickets drafted. Pick the ones to keep." No numbers such as #12, rows, chips, commands or the journal. Then say you wait for the user's picks with journal board wait , and finish with journal sequence next --about .