Tasks

#What Tasks does

The team's to-do list, tied to the projects it belongs to — so planning and delivery are the same list seen from two angles.

• Active and backlog, separated. Three views — All, Active and Backlog — so what you are doing this week is not buried under what you might do this quarter.
• Sub-tasks. Work that breaks down, breaks down. A task can carry its own steps without spawning a second board.
• Project-linked. A task attached to a project appears in that project, so the delivery view and the task list never disagree.
• Priority that means something. Status and priority per task, set where you work rather than in a separate planning ritual.

#Why it exists

Tasks live in three places: a project plan nobody updates, a chat message that scrolled away, and someone's head. Nothing tells you what is actually next.

One task list with status, priority and owner, attached to the project it serves. Tasks on a project show up in that project — one list, two views, nothing to reconcile.

#Plan and ship

Three views — All, Active and Backlog — so what you are doing this week is not buried under what you might do this quarter.

1. Create a task with a status, a priority and an owner.
2. Attach it to the project it belongs to — it then appears in that project too, so the delivery view and the task list never disagree.
3. Break work down with sub-tasks rather than spawning a second board for it.
4. Move finished work out of Active; the backlog is for what is real but not now.

#On the MCP surface

Your AI reads and writes tasks over MCP — it can plan out a project's next steps, set priorities and close what is done, without you leaving the conversation.

#On the Cloudflare side

• Tasks live alongside the rest of your project data — on the D1 database on YOUR Cloudflare account when one is connected.

#Works with

• Projects. Milestones, time logs and budget — per project.
• Tracked work. The hours your team logged, on a timeline and as timesheets.
• CRM. Contacts, companies and a weighted pipeline.