Purpose
Create reviewable tasks that can be synced into a task system or left as a proposed checklist.
When to use it
- A document or meeting contains scattered next actions.
- You need a task list before execution.
Inputs
- Source text
- Known owners
- Project context
Outputs
- Tasks
- Owners
- Due dates
- Evidence
Steps
- Identify verbs of commitment, request, review, and waiting.
- Normalize each task to one owner and one outcome when possible.
- Keep missing owners or dates explicit.
- Separate tasks from decisions and ideas.
Quality checks
- Every task has evidence.
- The task can be completed or verified.
Failure modes
- A broad goal is listed as a task.
- The agent creates a task from a rejected idea.
Privacy notes
- Tasks may contain sensitive customer or internal data.
- Review before creating tasks in shared systems.
Example prompt
Extract concrete tasks from this source. Include owner, due date, evidence, and missing information. Do not include rejected ideas.
Example structured output
{"tasks":[{"title":"Rebuild workbook with vendor cycle field","owner":"Shawn","due":null,"evidence":"note:12"}]}