jason.woltjeandClaude Opus 5.5
34a72af912
packages/queue, scripts/queue-commit.sh, scripts/git-hooks and scripts/test-queue.sh, plus docs/plans/BRIEF-TEMPLATE.md. There is no queue.json yet, so verify skips until the genesis commit after A2. Darkwing built it, and Filbert reviewed R0 (6933b885, changes requested) and r1 (e464be6c, approved). The 20 files match manifest 85a8a453. The nine suites passed on an index export, including the new queue suite. test-queue.sh joins the suite list in AGENTS.md. Lead decisions 20, 23 and 26. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1.4 KiB
Brief template
Copy the section below into the brief file for a queue row, one ##
heading per row. The row records the file path and that heading as its
brief anchor (--brief docs/plans/<file>.md#<heading>), plus the git blob
of the committed file.
Rules the queue enforces (queue-as-data plan 8.13):
- the brief is committed before
queue addor a brief change names it; a staged or untracked brief is refused; - the heading occurs exactly once in the file;
- a later edit to a committed brief makes
nextflag the row andstartrefuse until the lead re-pins it.
queued means the brief exists, not that it is accepted. The row moves to
briefed when a privileged actor (jason or sage) accepts it; the owner
can't.
<Piece name, the row's one-line piece text>
Problem
What is wrong or missing today, with evidence: file paths, issue numbers, command output. One paragraph.
Owner and reviewer
- Owner: the seat that does the work.
- Reviewer: the seat that reviews it, or "none" and why.
Files owned
Every path this piece may create or change. Anything else is out of scope unless the brief is amended.
What ships
The concrete result: code, tests, docs. Name the test suites that must pass.
Out of scope
What this piece deliberately leaves alone, and where that work goes.
Gate
Who says yes, and on what evidence: the command to run, the output to expect, or the comment to read.