During an interview the orchestrating agent tells the person about the question drafter's internal round trips: the drafter refused a draft for running one row over the 24-row limit, and the agent narrated that refusal, its reasoning, and the redraft it was resuming. The person does not need any of it. Only the finished question should reach them; a refused or redrafted question is the agent's own business.

Frontmatter

.abcd/work/issues/resolved/iss-2610161734179773-interview-narrates-question-drafter.md
open on GitHub ↗ · commit history ↗

mentions2

• iss-2610230745597968Questions still break abcd's asking limits after several rounds of fixes, on two accounts on 2026-10-23. (1) In a repository abcd manages, on another account, an agent bundled four separate issues into one question without going through the abcd:question-drafter agent, and the question check refused 21 parts at once: headers that were not role chips, no Decide later option, no Now: or Change later: lines, and question text that did not quote the thing being decided; the status line meanwhile read 'waiting on the product thinker'. (2) In abcd's own checkout, a question was refused because its text did not end with the question, and it also ran 25 rows against the 24-row limit (header and frame 8, question text 7, options 10), which the check reports but does not refuse, so it would have been shown and a narrow window might cut it; at the same time an abcd:question-drafter run spent 9 minutes 32 seconds and 174.2k tokens recounting over-limit tabs with a hand-written rows script. Earlier rounds include iss-2610071538055431, iss-2610100626327722, iss-2610161734179773 and the open iss-2610090816296964.
• itd-2610230756259215Every question abcd asks passes its check before the person sees it