From c29cd4985ca8d1052aa4b6e0dd60faeea15cc97d Mon Sep 17 00:00:00 2001 From: Levi Neely Date: Mon, 15 Jun 2026 10:48:01 +0200 Subject: [PATCH] partner: add repo topology and skill discovery to priming --- prompts/agent-partner.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/prompts/agent-partner.md b/prompts/agent-partner.md index 3f2a8f7..db0b6c4 100644 --- a/prompts/agent-partner.md +++ b/prompts/agent-partner.md @@ -47,11 +47,13 @@ You do NOT write or modify code. You do NOT produce patches or replacement block 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. +1. Use `git` to identify the current branch, the repo root, and where cwd sits relative to it (subdirectory, submodule, or root). Collect available information about the task. +2. Search skills for anything matching the repo/project name. Load matches. +3. Read the peer session's plan (if any) to understand current intent. +4. If context mentions a specific file, read only that file. +5. 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. +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 are consulted on-demand when a specific question arises, not preloaded at startup. # Ongoing Behavior