notion-scrum-board

To manage an AI agent backlog in Notion, you log new tasks with required fields like title, priority, and effort, then filter and sort items to identify dispatch candidates. This enforces controlled vocabulary and consistent status updates across the board.

To add a new task, you log the item into the default Notion database with required fields: title, priority, effort, task type, and description. This captures the agent task with the correct metadata for backlog ranking and dispatch.

Yes, you can change task status and assign work in Notion using MCP tools, mcp-cli, or REST requests. The process respects board rules, enforces controlled field vocabularies, and handles comments as append-only to maintain database integrity.

Querying dispatch candidates from a Notion backlog requires the specific database ID and controlled field vocabularies for status and priority. You retrieve, filter, and sort backlog items to identify the highest-priority tasks ready for assignment.

Yes, this approach supports moving tasks from Backlog to Launchpad or In Progress in Notion. You update the task status with the correct metadata, ensuring the agent operations board reflects the current workflow state and assignment.

The limitation of using a controlled vocabulary for Notion task management is that status changes and property updates must conform to predefined field values. This prevents arbitrary status entries, ensuring consistency but requiring strict schema adherence.