How do you give a Team a backlog so Bailey proposes what is next?

When is this the right size?

When a Team should own an outcome the way a human team does, not one person’s queue. The checkout service, fast and correct, no regressions to production: that is a scope with a backlog behind it, and the point of the size is that the Team picks what is next from that backlog, with a case, and you say yes or no.

How do you set it up?

On Create a Team, pick the repositories, then choose The backlog. Two more blanks appear: the project or epic the Team reads, picked from the tracker or pasted as a link, and the one sentence the Team owns. That sentence is its Responsibilities, and every line reads it as grounding. Click Create. Bailey comes on, supervised by you, alongside Wright, Reeve, and Proctor, and the small print says when it first runs.

If you already have a Team on your own tickets, you do not need a second one. Its page offers to let Bailey propose; switching that line on is the same size.

What does Bailey read?

The backlog the Team attaches: a Linear team, project, or saved view; a Jira project or epic; or a GitHub repository’s issues. Plus the Team’s Responsibilities, the decision ledger, and its own open proposals. A backlog still on its first sync is held, not read as empty. With no backlog attached and a tracker connected, the whole tracker is in view and the Responsibilities decide; with no tracker at all, Bailey proposes from the Responsibilities and the code.

What does a proposal look like?

A row under Proposed on Work, with the ticket’s key, its tracker assignee, and one sentence, and a case file behind it: why this ticket now, what it is expected to move, and the evidence it came from. The footer offers Start plan, which accepts it and hands it to Wright, or Doesn’t need work, which closes it with nothing planned and records the boundary Bailey found.

Bailey proposes a few at a time, on its rhythm, weekdays at 9 by default. Propose now on its line runs it once, whatever the clock says. Untouched proposals are withdrawn before a fresh set, and a proposal nobody answers in three weeks closes on its own.

Whose tickets does it pick from?

The Team’s from blank decides: anyone’s tickets in the backlog, the tickets assigned to named members, or unassigned ones. Members are matched to tracker accounts by email through the workspace connection, with a one-time Not you? if a match is wrong. Whatever it picks, the ticket keeps its key and its assignee on the row, and nothing changes hands in the tracker.

How does the rest of the Team work it?

Exactly as for any ticket. Accept and it moves to Plan; Wright drafts, Reeve critiques, you approve; Wright builds to a draft pull request; Proctor reviews; you merge. Your first ticket walks the whole path. What the backlog size adds is the front of it: a Team that argues for what is next instead of waiting to be told.

Can you change the backlog later?

Yes, on Bailey’s line, opened from the Team page. Its Backlog blank is a list grouped by what the Team already reads, then Linear, then Jira, with a search box under it for saved views, epics, and pasted links. Choosing one the Team does not have holds it in the sentence until you Save, which attaches it to the Team first and then rewrites the line, so a line never names a backlog its Team cannot read.