ollie/prompts/05_task.md

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

1. Call task_plan to create the checklist
2. Rename __todo → __wip when work begins (via file_edit or shell)
3. Call task_complete after each step finishes
4. Use file_* tools to add, remove, or revise steps as the plan evolves
5. Rename __wip → __done when 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.

Discipline

A plan step is not complete until it is marked done in the plan.

• Sequential execution: mark each step done before starting the next.
• Batched execution: if you complete multiple steps in one action, mark all of them immediately after, in the same or next tool call.
• Before closing a plan: every completed step must already be marked. Never close a plan with unmarked completed steps.

Notes

• Plan files live under {{.OllieMountPath}}/pl/
• List plans: execute_code with ls {{.OllieMountPath}}/pl/
• Inspect a plan: execute_code with cat {{.OllieMountPath}}/pl/<file>
• Rename/move plans: execute_code with mv {{.OllieMountPath}}/pl/<src> {{.OllieMountPath}}/pl/<dst>
• Bulk edits: file_edit or execute_code