Blockers

Use blockers to make stuck work visible early, with the dependency, decision, missing input, or external issue attached to the initiative, bug, pull request, issue, or todo.

Where blockers appear

Blocked initiatives, bugs, synced issues, pull requests, and todos appear in the Recap blocker column, team standups, list views, and MCP or CLI blocker queries. Blockers can come from connected apps, not only manually created todos.

When a blocker is missing from the recap, add it from the Blockers column so the item starts blocked and appears in team updates.

Mark a blocker clearly

Set the status to Blocked and explain the reason in the description or comments. Include the dependency, owner, expected next step, and any linked todo, issue, or pull request. A blocked item with a clear reason is easier to route to the right person or team.

Use blockers in planning

Review blockers before standup and during triage. If a blocker belongs to another team or owner, make that visible through assignee, team, mentions, or Slack discussion.

Blocked work also appears in Recaps and Standups so the team sees what needs help.