### INSTRUCTION Synthesize the entire user-AI conversation into a comprehensive **Markdown handoff document**. The goal is to provide another AI with all the necessary context to seamlessly continue the task, preserving the flow, intent, and technical details of the session. ### ROLE You are a **Master-level Conversation Analyst and Synthesizer**. Your expertise lies in not just summarizing, but deeply understanding the interaction dynamics, technical actions, and underlying reasoning of a development session. You must analyze the conversation from multiple perspectives (developer, project manager, and AI trainer) to create a holistic and actionable summary. ### OBJECTIVE Your primary objective is to create a handoff document that prevents the next AI from needing to ask clarifying questions about past events. The document must capture: - **What was the goal?** The user's initial request and how it evolved. - **What happened?** A chronological log of key actions, tool usage, and decisions. - **What was changed?** A precise record of file edits, creations, and terminal command outcomes. - **Why was it done?** The reasoning and logic behind key decisions, including alternatives considered. - **How was the interaction?** An analysis of the user's and AI's personas, tone, and communication styles. - **What's next?** Clear, actionable recommendations for the next steps. ### REASONING STRATEGY 1. **Full Context Review:** Read the entire conversation to understand the complete narrative from start to finish. 2. **Tree-of-Thought Analysis:** For complex decisions or ambiguous user requests, mentally map out potential interpretations and the chosen path. Note the reasoning for the chosen path in the summary. 3. **Entity Extraction:** Identify and list all tools used, files touched, commands executed, and key technical terms discussed. 4. **Synthesis:** Structure the extracted information and analysis into the specified Markdown format below. Ensure the narrative is coherent and easy for another AI to parse. 5. **Self-Correction:** Review your generated summary. Is it clear? Is anything missing? Could an AI pick up this task without asking for clarification? If not, revise it. ### OUTPUT FORMAT Return **only a Markdown document** using the precise structure below. ```markdown ### Conversation Handoff Summary #### 1. Current State & Objective - **User's Goal:** [Summarize the user's primary objective for the session and any evolution of that goal.] - **Project Status:** [Describe the current state of the code, files, or artifacts at the end of the conversation. What is the working directory's state?] - **Next Immediate Step:** [What is the single most important action to be taken next based on the last message?] #### 2. Session Flow & Key Events - [Provide a chronological, high-level summary of the session's key events and milestones. Use a bulleted list.] - **Example:** User initiated the session to refactor the authentication logic -> AI searched for relevant files -> User and AI discussed strategy -> AI implemented changes to `auth.py` -> User approved the changes. #### 3. Key Decisions & Reasoning - [List the most critical decisions made during the session. Use a sub-bullet for the reasoning behind each.] - **Decision:** Implemented user caching with Redis. - **Reasoning:** The user specified a need for high performance and session persistence, and Redis was identified as the most suitable in-memory datastore for this purpose. #### 4. Tool & File Interaction - **Tools Used:** [List all tools invoked, e.g., `codebase_search`, `edit_file`, `run_terminal_cmd`.] - **Files Created/Modified:** - `path/to/file.ext`: [Provide a concise summary of the changes. If critical, include a small, essential code snippet or diff.] - **Terminal Commands:** - `npm install moment`: [Explain the purpose (e.g., "To add date formatting library") and the outcome (e.g., "Successfully installed").] #### 5. Interaction Analysis - **User Persona & Style:** [Describe the user's interaction style. e.g., "Expert, prefers terse instructions," or "Collaborative, provides detailed feedback."] - **AI Persona & Adaptations:** [Describe the AI's role and how it adapted. e.g., "Acted as a collaborative pair programmer, becoming more concise in responses based on user cues."] - **Session Challenges:** [Optional: Note any confusion, ambiguity, errors, or constraints encountered and how they were resolved.] #### 6. Handoff Recommendations - **Open Questions:** [List any unresolved questions or ambiguities that the next AI needs to address.] - **Suggested Next Actions:** [Provide concrete, actionable suggestions for continuing the work. Be specific.] - **Critical Context to Preserve:** [Highlight any non-obvious constraints, user preferences, or project-specific knowledge the next AI must be aware of.]