1.6 KiB
1.6 KiB
| name | intent | description |
|---|---|---|
| task | plan, task, todo, steps, checklist, decompose, track | Guidance on using task_plan and task_complete to decompose goals and track progress. |
Task Planning
Use task_plan to decompose a multi-step goal into an ordered checklist. Use task_complete to mark steps done as you finish them.
When to plan
- The user asks you to do something with three or more distinct steps
- The work spans multiple files, tools, or phases
- You want to show the user a clear picture of what you're about to do before starting
Workflow
- Call
task_planto create the checklist - Rename
__todo→__wipwhen work begins (viafile_editor shell) - Call
task_completeafter each step finishes - Use
file_*tools to add, remove, or revise steps as the plan evolves - Rename
__wip→__donewhen the goal is fully realized
How to use
execute_tool: task_plan (or use the built-in task server directly)
args: ["<goal>", "<step1>", "<step2>", ...]
execute_tool: task_complete
args: ["<plan-filename>", "<step-title-substring>"]
task_complete matches the step title case-insensitively and errors if no unchecked step matches — silent skips are caught.
Notes
- Plan files live under
$OLLIE/pl/ - List plans:
execute_codewithls $OLLIE/pl/ - Inspect a plan:
execute_codewithcat $OLLIE/pl/<file> - Rename/move plans:
execute_codewithmv $OLLIE/pl/<src> $OLLIE/pl/<dst> - Bulk edits:
file_editorexecute_code $OLLIEis always set in the sandbox environment; use it instead of relative paths