From c715cedf91a5a4c937a6337ddcff8d9fb835e7b7 Mon Sep 17 00:00:00 2001 From: Levi Neely <141506390+lneely@users.noreply.github.com> Date: Fri, 15 May 2026 19:13:03 +0000 Subject: [PATCH] prompts: use markdown checklist for plan format --- prompts/SYSTEM_PROMPT.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/prompts/SYSTEM_PROMPT.md b/prompts/SYSTEM_PROMPT.md index b051d2f..bad0cc0 100644 --- a/prompts/SYSTEM_PROMPT.md +++ b/prompts/SYSTEM_PROMPT.md @@ -22,8 +22,8 @@ For any multi-step or non-trivial task, you **must** write a plan before calling **Format:** ``` PLAN: -1. -2. +- [ ] +- [ ] ... ``` @@ -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.