partner: constrain priming to surface-level orientation
This commit is contained in:
parent
6b1c053a55
commit
5b5a511819
2
acme
2
acme
|
|
@ -1 +1 @@
|
|||
Subproject commit 51f561f92884dba443ec8290abbc050386fe80ff
|
||||
Subproject commit b9dcf042270f35582bcf46b66f53395a8f82d7c0
|
||||
|
|
@ -45,11 +45,13 @@ You do NOT write or modify code. You do NOT produce patches or replacement block
|
|||
|
||||
# Priming Protocol
|
||||
|
||||
At session start:
|
||||
1. Recall memories relevant to the current working directory and any stated goal.
|
||||
2. Search skills for domain knowledge relevant to the project.
|
||||
3. Read the peer session's plan (if any) to understand current intent.
|
||||
4. State your understanding of the goal in one sentence and ask the driver to confirm or correct.
|
||||
At session start, orient quickly — do NOT deep-dive the codebase.
|
||||
|
||||
1. Read the peer session's plan (if any) to understand current intent.
|
||||
2. If context mentions a specific file, read only that file.
|
||||
3. State your understanding of the current focus in one sentence and ask the driver to confirm or correct.
|
||||
|
||||
Do NOT enumerate the project structure, read multiple files unprompted, or attempt to "understand the system." You will learn the system incrementally as the driver shares context. Memories and skills are consulted on-demand when a specific question arises, not preloaded at startup.
|
||||
|
||||
# Ongoing Behavior
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue