Refactor summary prompt for clarity and emphasis on deliverables

- Changed the title of the summary prompt to "THIS REQUEST'S SUMMARY" for better context.
- Revised instructions to focus on summarizing what was built/fixed/deployed/configured, rather than the observation process.
- Clarified when not to summarize, emphasizing conversational requests and trivial inquiries.
- Updated examples to better illustrate good summary practices.
This commit is contained in:
Alex Newman
2025-10-23 14:08:42 -04:00
parent f556546994
commit 33d2422faa
2 changed files with 21 additions and 31 deletions
File diff suppressed because one or more lines are too long
+5 -10
View File
@@ -156,24 +156,19 @@ export function buildObservationPrompt(obs: Observation): string {
* Build prompt to generate request summary * Build prompt to generate request summary
*/ */
export function buildSummaryPrompt(session: SDKSession): string { export function buildSummaryPrompt(session: SDKSession): string {
return `REQUEST SUMMARY return `THIS REQUEST'S SUMMARY
=============== ===============
Review the observations and create a summary of what was BUILT/SHIPPED. Think about the observations you just wrote for this request, and write a summary of what was built/fixed/deployed/configured, what was learned, and what's next.
CRITICAL: Describe what was delivered to the project, NOT what the memory system did. IMPORTANT! DO NOT summarize the observation process itself - you are summarizing a DIFFERENT claude code session, not this one.
User's Original Request: ${session.user_prompt} User's Original Request: ${session.user_prompt}
WHEN NOT TO SUMMARIZE WHEN NOT TO SUMMARIZE
---------------------- ----------------------
Do NOT create a summary if: Do not summarize if the request is conversational and unrelated to the work being done.
- **Already summarized**: This work was covered in a previous prompt's summary (check if it's just continuation)
- **Conversational banter**: User is chatting, joking, or making casual comments with no deliverables
- **Trivial requests**: Simple questions, status checks, or explanations that don't result in shipped work
- **No meaningful observations**: All observations were skipped or there's nothing substantial to document
- **Meta-discussions about memory**: Talking about the memory system itself without shipping changes to it
If any of these apply, **output only**: <skip_summary reason="[brief reason]" /> If skipping, **output only**: <skip_summary reason="[brief reason]" />
✅ GOOD - Describes deliverables: ✅ GOOD - Describes deliverables:
<request>Fix authentication timeout bug</request> <request>Fix authentication timeout bug</request>