dusk bot
routineslinear sprint recap

dusk botroutines

recap a linear cycle before the sprint closes

take unfinished issues into sprint review while the team can still decide what happens to them. this linear recap reads one team’s cycle on its closing day.

by the dusk bot team · checked · how we made this

it groups the issues by their current state and brings open work into dusk chat by name. the team decides what to carry forward.

pixel art: a yellow pixel bot and a blue pixel bot beside the Linear mark on a white tile, a signpost and a folder of papers, on a grassy meadow in front of an open blue sky, one saying "carry this forward"

the message

paste this into a chat with your bot

every weekday at 2pm, read the cycles for the mobile team (id 593bf852-7cf8-483b-b27e-2f658d545c3c) in linear. use the europe/london time zone. continue only if a cycle ends on today's local date. fetch that team's issues across all pages, including archived ones. match by cycle id. read issue details when membership is unclear.

in this chat, name the cycle and snapshot time. give completed and canceled issues separate lines with id and title. for each remaining issue show id, title, state, and assignee if present. ask which open items should carry over. never move an issue, change its state or assign it.

stay silent if no cycle ends today or the cycle has no issues. if missing data could change that conclusion, report the gap.
when
weekdays at 2pm in the team’s time zone, with a recap only on a cycle’s closing date
needs
linear read only for the team’s cycles, team issues and individual issue details. use your linear team id, name and time zone.

what comes back

an example, not a real run

mobile · cycle 18 · friday 14:00
complete: mob-84 · restore saved filter
canceled: mob-81 · remove old help tab
open: mob-88 · retry interrupted upload · in review · ruth dale
carry mob-88 forward, or finish the review this afternoon?

make it yours

  • match the meeting. if the review falls a day early, ask for the cycle ending tomorrow. label the snapshot with today’s date.
  • use your workflow states. give the bot your definitions for complete and canceled. identify review states that still require a decision.
  • put a name beside the carryover. if several issues remain, group them by assignee. keep unassigned work visible.

when it goes wrong

  • the wrong sprint appears. two teams can have a cycle with the same number. read the team’s cycle id before selecting issues.1
  • a canceled item sounds like a delivery. keep cancellation separate even when neither item needs further work.
  • the recap and the meeting disagree. look at the snapshot time. an issue completed during the meeting still appears open in an earlier recap.

what the recap can tell the team

use the open list to make one decision per issue. should someone finish the review today, split the remaining work, or put it back in the backlog? the issue id keeps that discussion attached to the right piece of work.

if you need the exact scope the team committed to on day one, this snapshot is the wrong pick. an issue moved out of the cycle before the run won’t appear.

questions

does a completed issue mean the change shipped?

it means the issue reached a state your team calls complete. confirm deployment separately before telling a customer the change is live.

can i use the same routine for two-week sprints?

yes. the end date selects the cycle. the bot looks on weekdays and stays quiet between closing dates. include a weekend day if your cycles finish then.

sources

  1. composio: linear actions, checked 12 november 2026
  2. dusk bot docs: routines
  3. dusk bot docs: connected apps

drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].