AI Prioritization & Triage

It watches every card so the standup doesn't have to.

Blocked-task detection and next-up suggestions, built from signals already on your board. No black box - here is exactly what it reads and how far to trust it.

Blocked-task detection

A card that stops moving is the earliest sign of trouble, and the easiest to miss. KITEBED flags any card that crosses a threshold you set for time-in-stage with no comment or activity - before it costs the team a week.

Thresholds are per-workflow. A design task and a hotfix should not be judged stale on the same clock, so they aren't.

In Progress3
Bug triage - session drop
SD 2d, no activity
blocked 2 days
DB migration - v2 schema
MK waiting on review
blocked, awaiting review
Auth refactor
LN due Fri
prioritized, due Friday
The signals it uses

Prioritization from what is already on the board.

Next-up suggestions weigh four signals. Nothing hidden, nothing scraped from outside your workspace.

Time in stage Comment & activity gaps Dependency status Due-date proximity

An honest note on reliability

Triage is a strong assistant, not an oracle. It is accurate on clear-cut cases - a card untouched for days, an obvious dependency chain, a deadline bearing down. On ambiguous work it surfaces a suggestion for a person to confirm, never a silent decision. Every flag and every priority is visible, explainable and easy to override. You stay in control; the AI just makes sure nothing goes unnoticed.

How a suggestion is made

From raw signal to a ranked next step.

1

Read the board's own signals

Time-in-stage, comment gaps, dependency links and due dates - all already present on your cards, nothing scraped from outside.

2

Weigh them against your thresholds

Each workflow sets its own limits, so a hotfix and a design task are never judged stale on the same clock.

3

Surface it with the reasoning attached

The flag or ranking appears on the card with a plain-language why, so a person can confirm or override in a click.

Set the thresholds, keep the control

Triage is tuned by you, not imposed. Decide how long is too long for each stage, which fields count toward priority, and where a flag should show up. The system does the watching; you set what "stuck" means.

  • Per-workflow staleness thresholds
  • Priority weighting you can adjust
  • Flags routed to the board, chat, or a digest
  • Every suggestion explainable and reversible

What it deliberately won't do

It won't move, close or reassign a task on its own, won't hide its reasoning, and won't invent urgency that isn't backed by a signal. Triage is an early-warning layer over your board - it points, it never decides. The moment a suggestion needs judgement, it hands that judgement to a person.

Let the board flag what's stuck

Turn on triage and stalled work starts surfacing on its own - with the reasoning shown on every card.