We just finished sprint review. Take the transcript, pull what carried over, what we decided to do next, and the new bugs raised, then build the next sprint plan with points and owners against our 40-point capacity.
Reading the review transcript to separate carry-over work, new commitments, and bugs raised.
Reconciling the transcript against the board and open PRs so nothing is double-counted.
Reconciling with the board3 stepsPull carry-over from Cycle 24
Check open PRs for near-done workFile the 2 new bugs from the demoBuilding the plan to fit 40 points with Tom out the back half.
Built. Next cycle plans to 39 of 40 points: carry-over ENG-412 (3 pts), the cut dunning retries now top priority (8 pts), the activation guardrails from this week's incident (5 pts), the two demo bugs (3 pts), plus the next themed batch. I down-weighted Tom's load since he's out the back half. The full sprint plan is in Libra Computer.
Create Cycle 25 and assign issues in Linear
Spins up the cycle, sets points and owners, and links carry-over to its prior issue.
Draft · not sent
⠇ThinkingESC to interrupt
Waiting for LLM...·0ms·- tok/s·1/45
10 / 10