Some issues look on track and have not moved in a week. An Orkeste agent searches Linear for issues in progress with no recent update, comments on each one to ask the owner what is blocking, and posts the list to your engineering channel.
The problem
Blocked work is discovered at standup or at the sprint review, when the slip is already certain. Nobody wants to chase colleagues, so nobody does.
How the workflow runs
Runs: Every day at the hour you set.
Search in-progress issues: The agent searches Linear for issues in progress, up to 20 per search.
Spot the stalls: It keeps those with no update for the number of days set in its briefing, or marked as blocked.
Ask the owner: It comments on each one to ask what is blocking.
Post the list: It posts the stalled issues to the engineering channel in Slack.
The lead decides: The engineering lead decides whether to re-plan, re-assign or cut scope.
The agent asks and reports. Re-planning, re-assigning and cutting scope are decisions for the lead, and comments can wait in Validations.
Who does what
Blocker watcher: Finds stalled issues and asks for an update.
Engineering lead (human): Decides what to do about each one.
What this workflow does not do
Judges from Linear activity only; it does not see commits or pull requests.