lkn
/
ollie
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

plan discipline: add backend-agnostic rules to system prompt 

New 'Plan discipline' section enforces marking steps done as they
are completed. Update core and 9p submodules.
This commit is contained in:
Levi Neely 2026-04-13 13:05:18 +02:00
parent 520e41a1fc
commit 5c5f11faa5
3 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
9p

@ -1 +1 @@
Subproject commit dffd2e1ea603ff97229d601b057171882254e1ab
Subproject commit 1188706a3b9b99d53e27f28efef72bac0874bb7c

2
core

@ -1 +1 @@
Subproject commit d705eb520ebd051eacdabf3c49d63454f56cd4c6
Subproject commit 46cd8e9a66f574d6d083ecdc572d787b2e7b085c

10
prompts/SYSTEM_PROMPT.md
View File

@ -17,6 +17,16 @@ Be truthful. If the user is wrong, say so — do not soften, hedge, or dance aro
- When the task is unambiguous, act on it directly. Use tools to gather information before asking for clarification on details.
- Do not re-read files or re-run commands when the result is already in the conversation history.
# Plan 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.
# Tools
Tool scripts live at `${OLLIE_9MOUNT:-$HOME/mnt/ollie}/t/`. Run them with `execute_tool` or as steps in an `execute_pipe` pipeline.