Last active
September 25, 2025 16:44
-
-
Save sxalexander/d1568048b348c3ea9df75f4489bbac95 to your computer and use it in GitHub Desktop.
Use this prompt when you need to move from one chat to another
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Your task is to create a detailed summary of the conversation so far, paying close attention to the user's explicit requests and your previous actions. | |
| This summary should be thorough in capturing business details, priorities, process patterns, and decisions that would be essential for continuing work without losing context. | |
| Your goal is to create a thorough summary that preserves business details, priorities, process patterns, and decisions. This summary must be detailed enough that work can continue seamlessly based on the information provided. | |
| Before writing your final summary, you must first conduct a thorough analysis. Write your analysis inside <analysis> tags and follow this process: | |
| 1. Read through the entire conversation chronologically | |
| 2. For each message and section, identify: | |
| - The user's explicit requests and stated intents | |
| - Your approach and responses to those requests | |
| - Key decisions, concepts, and patterns that emerged | |
| - Specific details including names, companies, business information, analysis results, full quotes, deliverables, drafts, and any other concrete details | |
| 3. Pay special attention to the most recent messages to understand what was being worked on immediately before this summary request | |
| 4. Double-check that you've captured all essential elements thoroughly and accurately | |
| After completing your analysis, provide your summary inside <summary> tags with exactly these sections: | |
| 1. **Primary Request and Intent:** Capture all of the user's explicit requests and intents in comprehensive detail | |
| 2. **Key Concepts:** List all important concepts, inputs, decisions, and frameworks that were discussed throughout the conversation | |
| 3. **Document Sections:** Enumerate specific messages, documents, or content sections that were examined, modified, or created. For each document or section: | |
| - Add exact relevant document sections in <document source="title of doc"> tags with exact citations. | |
| - Explain why this document/section is important | |
| - Summarize any changes or modifications made | |
| - Include relevant full quotes or snippets where applicable | |
| Pay special attention to the most recent work and include verbatim content where relevant | |
| 4. **Problem Solving:** Document what problems were solved and describe any ongoing decision-making processes or analytical work | |
| 5. **Pending Tasks:** List any tasks that you have been explicitly asked to work on but have not yet completed | |
| 6. **Current Work:** Describe in precise detail what was being worked on immediately before this summary request. Focus heavily on the most recent messages from both user and assistant. Include specific document names, code snippets, quotes, or other concrete details about the active work | |
| 7. **Optional Next Step:** Only if there is a clear next step that directly continues the most recent work, describe what that step would be. This must be: | |
| - Directly aligned with the user's explicit requests | |
| - A continuation of the task you were working on immediately before this summary request | |
| - Supported by direct quotes from the recent conversation showing exactly what task was in progress | |
| If your last task was concluded or if the next step is unclear, do not include this section. Do not suggest tangential work without explicit user confirmation. | |
| Important requirements: | |
| - Be thorough and specific in all sections | |
| - Include direct quotes and verbatim content where relevant, especially for recent work | |
| - Focus particularly on the most recent messages to capture current context accurately | |
| - Ensure the summary provides enough detail for seamless work continuation | |
| - Only suggest next steps that are explicitly supported by the conversation content |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment