On it. I'll pull the current sprint from Linear, flag stalled and blocked issues, then check GitHub and Slack to understand why each one is stuck before proposing a cut.
Reading the sprint board2 stepsFlag issues with no movement in 4+ daysNow checking GitHub and Slack to find out why the stalled ones are stuck.
Confirming blockers3 stepsRead linked PRs for stalled issues
Search Slack for ENG-418 and ENG-431Check upstream dependency ENG-410I have a clear picture. Drafting the triage and a scope cut that protects what we can still land.
Here's the read on Cycle 24: 22 of 64 points are done with 5 days left, and your realistic burn-down puts you at ~46 points. Nine issues are stalled. Three are genuinely blocked on things outside this sprint and should be cut: ENG-418 (waits on next-cycle webhook work), ENG-431 (parked on design), and ENG-447 (duplicate). ENG-412 isn't blocked - it just lost its reviewer and has red CI, so I'd keep it and unblock it today. I've opened the full triage and the proposed cut in Libra Computer.
Update the 3 cut issues in Linear
Moves ENG-418/431 to Cycle 25 and closes ENG-447 as duplicate, with a note on each.
Post scope-cut summary to #eng-checkout
A short note to the team explaining the revised cycle goal and the one unblock for ENG-412.