Public: anyone can read this; the crew can change it.

The week is the sprint: a cut line on Next up shows what this week's capacity can ship, and the forge writes its own retrospective #8704

Closed opened this has it

Landed in pull #8809 · run

opened this

The owner, 2026-11-02: scrum's planning and retrospective, with the product owner prioritizing and developers estimating, gives capacity and projections. A direct mapping would not suit the forge, but the idea holds for agents.

The mapping: the subscription's weekly reset is the sprint boundary, and the week's remaining usage is capacity. The owner ranks (#8694). The forge estimates from measured history rather than asking agents to guess. There are no ceremonies and no locked scope: rerank any time and the line moves. Builds on #8694, #8695 and #7815.

Done when:

4 earlier comments
commented

From Linear's cycles and project graph (https://linear.app/docs/use-cycles, https://linear.app/docs/project-graph): capacity is measured from the last three periods, and with no history it counts every issue as 1. Projections are a range of about 40% either side. Unfinished work rolls over by itself, so no re-deciding is needed. The retrospective is a frozen snapshot, written once. Add a health mark per group: green, yellow, red, and gray for nothing said lately, which is the stall signal.

commented

The cut line falls between whole bets or scopes (#8713), never mid-scope, since half a whole isn't shipped. Unfinished bets do not roll over by themselves here: they stop at appetite, and re-backing is one tap. This overrides my earlier note on rollover.

commented

Reviewed pull #8809 at its head: ticked Each issue on Next up shows a cost estimate as a range, from past runs of similar size and kind, and says when it has too little history to tell.; A projection in one sentence: what should ship by reset at the current rate, and how sure.; At each reset the forge writes one screen, without being asked: what shipped against the projection, estimate accuracy, what cost most for least, and what got stuck and why. It ends in at most three proposed changes, each one tap to accept. Nothing changes without that tap (#7815).; The same state gives the same estimate and line (tested), and no agent run is spent producing an estimate.. left open: A cut line on the list shows what fits in the week's remaining capacity, and moves live as the list is dragged. Issues below it read as next week. — The cut line and the next-week reading work, but the line moves only after the drop and a server reload, not live during the drag..

commented

Left open after pull #8809 landed: 1 unticked item remains (A cut line on the list shows what fits in the week's remaining capacity, and moves live as the list is dragged. Issues below it read as next week.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

commented

The open box is now #8858. The cut line is drawn today, but it only moves after the drag's save reloads the page, so #8858 makes it move during the drag.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs