Task
Execution unitTasks are where missions become launchable work.
Workflow
Tasks
Tasks convert mission intent into executable lanes. They are useful when work should be assigned, prioritized, split, retried, or reviewed independently.
Guide summary
Use this page to understand the surface before you act inside it.
Use tasks as execution-ready work units inside a mission.
Guide type
WorkflowThis guide reflects the current product workflow and surface ownership.
Sections
7Summary first, then steps, mistakes, and recovery notes.
Related guides
3Written against the current product structure and core execution workflow.
Best use
Split complex workResearch, review, and packaging often deserve separate lanes.
Related action
Review task scope before launchWell-scoped tasks create cleaner runs and clearer artifacts.
Guide section
What it is
A task is an executable work unit attached to a mission or standalone objective.
When to use it
Use tasks when work needs multiple lanes, separate ownership, staged delivery, or clearer prioritization.
Where to find it
Find tasks in the Tasks index and linked from mission detail surfaces.
What happens next
You use this surface as part of the broader mission -> task -> run -> artifact workflow.
Common mistake
Making one task too broad
Related action
Use task runs to isolate failures instead of retrying an entire mission-shaped block of work.
Guide section
Why it matters
It lets you assign responsibility, status, priority, and context at a smaller scale than the mission itself.
Guide section
How it fits into the workflow
Tasks sit between mission framing and run execution.
Guide section
Step-by-step usage
- Name the task in execution terms.
- Assign the most suitable operator or plan lane.
- Attach context if the task needs it.
- Set priority or status posture.
- Launch a run from the task when it is ready.
Guide section
Inputs and outputs
Inputs needed
Clear work unit
Optional operator assignment
Optional context
A mission if the task belongs to a broader objective
Outputs produced
Launchable task records
Cleaner work segmentation
Better retry and review boundaries
Guide section
Common mistakes
- Making one task too broad
- Leaving assignment ambiguous
- Creating many tiny tasks with no real operational benefit
Guide section
Troubleshooting
If tasks feel noisy, consolidate adjacent work. If runs are chaotic, split oversized tasks into cleaner lanes.