prompts: compress tools-task to match other tool prompt style

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Levi Neely 2026-04-26 13:06:09 +02:00
parent 68246cd527
commit e44874bec5
1 changed files with 12 additions and 39 deletions

View File

@ -1,47 +1,20 @@
# Task Tools
A session-scoped markdown checklist at `s/$OLLIE_SESSION_ID/plan`. Survives
compaction. Visible to peers at `s/{your-session-id}/plan`.
A session-scoped markdown checklist at `s/$OLLIE_SESSION_ID/plan`. Survives compaction. Visible to peers.
Use this for concrete, low-level actions within the current session:
"edit file X", "change function Y", "run tests". If beads is also present,
plan items should be derived from the claimed bead.
**Trigger condition**: before writing any file or running any command, add tasks for the work ahead. Do this even for short jobs.
## Commands
| Tool | Effect |
|---|---|
| `task_add <task> [task2 ...]` | Add one or more tasks |
| `task_check [n]` | Check off task n (1-indexed); defaults to first unchecked |
| `task_clear` | Remove all completed tasks |
Read the current plan at any time:
**Calling convention**:
```
execute_code: steps=[{tool: "file_read", args: ["$OLLIE/s/$OLLIE_SESSION_ID/plan"]}]
execute_code: steps=[{tool: "task_add", args: ["step one", "step two", "..."]}]
execute_code: steps=[{tool: "task_check", args: []}]
execute_code: steps=[{tool: "task_clear", args: []}]
```
## Workflow
**Returns**: confirmation.
**Before writing any file or running any command**, add tasks for the work ahead. Do this even for short jobs — the plan survives compaction and lets you recover if context is lost.
```
execute_code: steps=[{tool: "task_add", args: ["read auth middleware", "identify the bug", "write fix", "run tests"]}]
```
Check off each step as it completes:
```
execute_code: steps=[{tool: "task_check"}]
```
Clear completed tasks when the list gets long:
```
execute_code: steps=[{tool: "task_clear"}]
```
## Coordination
Peers and parent sessions can read your plan directly. When spawning a
subagent, include your session ID so the subagent can observe your progress:
```
Your parent's plan: s/$OLLIE_SESSION_ID/plan
```
**Constraints**:
- `task_add`: adds one or more tasks in order.
- `task_check [n]`: checks off task n (1-indexed); defaults to first unchecked. Call after each completed step.
- `task_clear`: removes completed tasks. Call when the list gets long.
- When spawning a subagent, pass your session ID so it can observe your plan at `s/$OLLIE_SESSION_ID/plan`.