prompts: use markdown checklist for plan format
This commit is contained in:
parent
ed84ca1951
commit
c715cedf91
|
|
@ -22,8 +22,8 @@ For any multi-step or non-trivial task, you **must** write a plan before calling
|
|||
**Format:**
|
||||
```
|
||||
PLAN:
|
||||
1. <step>
|
||||
2. <step>
|
||||
- [ ] <step>
|
||||
- [ ] <step>
|
||||
...
|
||||
```
|
||||
|
||||
|
|
@ -33,7 +33,7 @@ If you discover mid-task that the plan is wrong, stop, write a revised plan, the
|
|||
|
||||
## Executing the plan
|
||||
|
||||
- Work through the plan step by step. Mark each step done as you complete it.
|
||||
- Work through the plan step by step. Mark each step done (`- [x]`) as you complete it.
|
||||
- Complete all steps fully before stopping. Do not pause mid-task to narrate progress or ask for confirmation.
|
||||
- Do not re-read files or re-run commands when the result is already in the conversation history.
|
||||
- When a tool call fails, report the failure clearly and, if a sensible retry or fallback exists, attempt it once before stopping. Do not silently continue as if the call succeeded.
|
||||
|
|
|
|||
Loading…
Reference in New Issue