Files
stack/docs/plans/BRIEF-TEMPLATE.md
T

1.8 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 add or 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 next flag the row and start refuse 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.

Handoffs

Every seat hands off directly (DECISIONS Q210, mos-1221). When the owner pushes a build or a new round, or the reviewer posts a verdict, that seat messages the next seat's T3 thread and Sage's with mcp__t3__t3_send_message. Claude and Codex seats both have it. Copy Mos's thread only when Mos has a step. Nobody waits on a date or a schedule when the next step is ready.