# Task-Driven Workflow
SUMMARY: Use Synapse tasks to drive multi-step LLM workflows that survive across sessions.

Task-Driven Workflow
Tasks aren't just todos — they're the backbone of persistent LLM workflows.
By creating tasks for multi-step work, you ensure continuity across sessions
and provide audit trails for what was done.
Why Task-Driven?
Without tasks:
- LLM starts each session unsure what to do
- Multi-step work is forgotten mid-execution
- No record of what's been done
With tasks:
- LLM resumes in-progress tasks immediately
- Multi-step work survives across sessions
- Built-in audit trail of all work
The Pattern
[CODE BLOCK]
Implementation
Step 1: Create a task for multi-step work
[CODE BLOCK]
Step 2: Track progress in task description
[CODE BLOCK]
Step 3: Resume across sessions
[CODE BLOCK]
Step 4: Complete and archive
[CODE BLOCK]
Full Example: Deploy Workflow
[CODE BLOCK]
Task Hierarchy
For complex work, use parent-child task relationships:
[CODE BLOCK]
Search for sub-tasks:
[CODE BLOCK]
Status Workflow
[CODE BLOCK]
Pending
Task created but not started. Use for planned work.
In Progress
Currently being worked on. Update description with progress.
Done
Completed successfully. Description should include summary.
Cancelled
Abandoned. Description should include reason.
Best Practices
> [!TIP]
> - Create tasks for multi-step work — single-step work doesn't need a task
> - Update description with progress — enables resumption
> - Use high priority for active work — surfaces in recall
> - Complete tasks when done — don't leave them inprogress
> - Store completion summaries as memories — long-term reference
Common Patterns
Pattern: Bug Fix Workflow
[CODE BLOCK]
Pattern: Research Workflow
[CODE BLOCK]
Next Steps
- Session Start Pattern
- Chat Polling Pattern
- Error Recovery