Review tickets with your AI designer¶✎ edit
Open it from the pipeline with ai:review: it opens on the tickets the pipeline is showing (its role, status, kind, mine). Narrow them with Role and State (on a phone, the two drop-downs on top), or Only with questions.
For each ticket your designer gives you:
- In short: what it is and why, in a few lines;
- the Overview, as the ticket writes it (folded when it has questions);
- its questions, each with the designer's pick first.
Pick what fits it: Answer and send on for a question; Send, Hold, Pause, Park or Drop for a ticket waiting on you; Hold, Pause, Park or Drop for one in work. Add a note in your words if you want; it goes on the ticket. A decided ticket turns green, and the review moves to the next one.
Jump around by pressing any ticket on the left; ← back to P-n takes you to the one before. Ask your designer about the ticket you're on; the answer comes in the chat.
Carry them out at the bottom does every pick at once, as your word: each is recorded as your decision, your notes go on their tickets, and you get one summary. Each ticket carried out fades from the list (one you held stays).
Your review is kept as you go: a reload, or the same review on your phone, opens where you were.
Vim mode: j/k next and back, a s d f… pick an option (each button shows its key), i to write in the box, Esc to leave it. The keys never fire while you type.
Notices¶✎ edit
ai:Review on Notices opens the same review on your notices of every project: one row per kind of notice, as Notices groups them. For each one your designer says what it is in plain words and whether it needs you, with its options, its pick first: Clear, Keep, Ask ops (a system alert), File a ticket (written by the designer, held for your send) or Goes with P-n (an item that already fixes it). Clear and Ask ops are your own calls from the page; a ticket and a note go to the designer as your word. Your designer never clears a notice itself. A notice cleared that fires again comes back marked ↺ came back, its write-up kept.
Ask about a notice in the box under it: the answer comes on the notice, under your question, and its chip moves ❓ asked → ✍ answering → 💬 answered. The review talks to your designer in the background: the chat isn't opened for it.
Agent skills¶✎ edit
The skills for agents working this page, one per request it sends, each with its key (the heading's anchor: ticket_review, notice_review…). Ask d2 for one by its key, and read it whole.
Write the ticket abstracts¶✎ edit
Asked as: review my tickets, go through what I have to send, walk me through the pipeline. The line: ai:review: write the abstracts (TicketReview:<id>). Write each ticket's short (a few plain lines from its Overview) and its questions (your pick first) onto the review's items, then set the review ready. How to write the review: #review_write.
Write the notice abstracts¶✎ edit
Asked as: go through my notices, what are these warnings, clean up my notices. The line: ai:review: write the notice abstracts (TicketReview:<id>). The review has of: notices, with items keyed c:<code>. Read the notices (GET /api/v2/d2/Notice) and write on each item: short (what it is, and whether it needs the person), options (any of clear, keep, askops, ticket, goes), rec (your pick), and ticket: {title, summary} for a ticket or goesWith: "P-n" for an item that fixes it. Then set the review ready. Never clear a notice yourself.
Answer a question on an item¶✎ edit
Asked as: a question typed in the review's box about the ticket or notice it is on. The line: ai:review: about … (TicketReview:<id>): <question>. Answer on that item, never in the chat. Set its ask to answering, write the answer in the a of its last qa entry, then set ask to answered. Change short, rec or ticket if the answer changes them. Keep each answer to the setting review.answerChars (1,200 by default): the point, then links. In the chat, one line at most.
Carry out the picks¶✎ edit
Asked as: Carry them out, do what I picked. The line: ai:review: … carry them out, as my word. Do each line as the person's word: file the tickets (held for their send), note the items, and report in one short chat line.
Write the review¶✎ edit
Asked as: (used by the others) save to the review, update the review. GET, then PATCH /api/v2/d2dom/TicketReview/<id> {items} with If-Match: v<ver>. On a 409, read it again and redo your change. One review is one d2 object, with a size cap.