Task Management
Create, assign, link, and complete tasks across every part of your business - with AI assignment, dependencies, and automatic memory capture.
Stop losing track of what needs to happen next. Create tasks, link them to customers and transactions, assign them to your AI, and let dependencies handle the sequencing.
What you can do
“Create a task to follow up with Acme Corp by Friday.”
“What’s overdue? What’s blocked?”
“Mark the SOW task as done - they pushed back on pricing but we closed at $600/mo. Remember that for future deals.”
“What did we ship last week? Turn it into a LinkedIn post.”
“What’s falling through the cracks?”
Your AI becomes your task manager, accountability partner, and weekly review generator.
Tools
Task lifecycle
| Tool | What it does |
|---|---|
create_task | Create a task with title, due date, priority, tags, and optional entity links |
update_task | Change any field on a task - status, priority, tags, due date, dependencies |
complete_task | Mark done with a completion note. Optionally store the note as org memory. Returns any tasks that were waiting on this one. |
remove_task | Remove a task (soft delete - recoverable) |
assign_task | Reassign a task to a person or to @claude for AI execution |
get_task | Full detail on a single task including what it blocks and what blocks it |
Organization and search
| Tool | What it does |
|---|---|
list_tasks | Browse tasks with filters for status, priority, scope, tag, assignee, and due date |
get_task_summary | Aggregate counts by status, priority, and assignee |
add_task_note | Add a note to a task without changing its status |
Entity linking
| Tool | What it does |
|---|---|
link_task | Connect a task to a customer, contact, interaction, transaction, project, playbook, or memory |
unlink_task | Remove a link |
list_entity_tasks | Find all tasks linked to a specific entity |
Related surface tools
These cross-domain views live in the Surfaces module but are especially useful for task-centric workflows:
get_session_start- Morning dashboard with overdue tasks, AI queue, finance pulse, cold customers, unread feeds, and suggested actionsget_weekly_retro- Completed tasks grouped by tag with notes. Setformat: 'linkedin'for a ready-to-post draft.get_stuck_list- Stale, blocked, and overdue tasks sorted by worst offenders with triage suggestionsget_entity_card- Complete picture of any customer, contact, or transaction including all open tasks
Key concepts
Dependencies
Set blocked_by_task_id when creating a task and it automatically enters “blocked” status. When you complete the blocker, the response tells you which tasks are now unblocked. No manual status juggling.
AI assignment
Assign tasks to @claude and your AI picks them up. When completing AI-assigned work, always include a completion_note so the outcome is captured.
Task-to-memory bridge
Set store_as_memory: true on complete_task and the completion note gets persisted as a searchable org memory with semantic embeddings. Great for capturing pricing decisions, customer preferences, or lessons learned - things that matter beyond the task itself.
Entity linking
Tasks can link to any entity in the system: customers, contacts, transactions, or memories. Use get_entity_card to see all open tasks for any entity in one call.
One owner per task
Every task has exactly one assignee: the single accountable owner, the “one neck to grab.” This is a deliberate design choice. When a task is assigned to a group, it tends to get done by no one, because nobody clearly owns the outcome. So Founders OS asks you to name one owner.
That does not mean only one person can be involved. When several people are part of the work, set the one accountable owner and name the others in the task description, or use @person tags for anyone you are waiting on. You get the clarity of single ownership without losing the context of who else is in the loop.
Real-world example
You: "Remind me to send the revised SOW to Acme by Thursday.
Link it to their customer record. Tag it #sales."
AI: create_task({
title: "Send revised SOW to Acme",
due_date: "2026-04-16",
tags: ["#sales"],
links: [{ entity_type: "customer", entity_id: "acme-uuid" }]
})
Done. #sales was auto-registered in the tag registry.
---
You: "SOW is sent. They negotiated down from $800/mo to $600/mo
on support. Remember that."
AI: complete_task({
task_id: "...",
completion_note: "Acme negotiated support from $800 to $600/mo.
Enterprise prospects treat support tier as negotiable.",
store_as_memory: true,
memory_project: "sales"
})
Done. One task unblocked: "Schedule demo with CTO".
Learning stored in org memory.