This prompt helps you create a comprehensive summary and action plan for meetings by identifying objectives, summarizing discussions, and listing decisions and action items. It ensures clear documentation and accountability for meeting outcomes.
Summarize the meeting transcript by performing the following tasks: - **State the Meeting Objective**: Begin with a brief paragraph (2-3 sentences) explaining the overall objective or purpose of the meeting based on the content provided. - **Meeting Summary**: Write a concise summary paragraph (5-8 sentences) capturing the main topics discussed and general outcome. - **Meeting Title**: Create a clear and descriptive title for the meeting. - **Discussion Points**: List the key discussion points addressed during the meeting in bullet points. - **Decisions Made**: Summarize all concrete decisions, resolutions, or agreements reached. - **Action Items**: List all action items, each assigned to a specific individual, including due dates if mentioned. Ensure that your output follows this order: 1. Meeting Title 2. Meeting Objective 3. Meeting Summary 4. Key Discussion Points 5. Decisions Made 6. Action Items & Responsibilities **Reasoning Order**: - First, identify the objective and content of the meeting, reason through the important points, summarize, and then state any conclusions such as assigned tasks, decisions, etc. - Do not start with conclusions or lists—always present the reasoning/summary before results or actionables. **Output Format**: Use markdown formatting, with clearly labeled sections and bullet lists where appropriate. Output should be ~2-3 paragraphs for objectives and summary, with bullet lists for points, decisions, and action items. **Example Output** (fill in with actual meeting details as appropriate): Meeting Title: [Descriptive Title of Meeting] **Meeting Objective:** The objective of this meeting was to review the status of the upcoming product launch and address any outstanding challenges. Participants discussed current progress, identified roadblocks, and set clear next steps to ensure timely delivery. **Meeting Summary:** During the meeting, team members shared updates on marketing, engineering, and logistics. Several potential delays were identified, and alternative solutions were brainstormed. The group agreed on prioritizing bug fixes and accelerating outreach efforts. Key deadlines were reaffirmed, and new responsibilities were assigned to address gaps in readiness. **Key Discussion Points:** - Progress updates from each department - Major blockers and proposed solutions - Resource needs and reallocations - Communication plan moving forward **Decisions Made:** - Proceed with expedited bug-fix schedule - Shift two resources from support to engineering until launch - Approve new marketing materials **Action Items & Responsibilities:** - [Alice] Finalize bug list by Friday - [Ben] Update marketing assets by next Wednesday - [Chloe] Coordinate logistics with new suppliers by end of week **Important:** - Always begin with objective and summary before listing points, decisions, or action items. - Be concise, clear, and accurate in capturing meeting highlights. --- **Reminder:** - Always capture the meeting objective and provide a summary first, then enumerate key points, decisions, and responsibilities. - Assign all action items explicitly to individuals. - Begin output with a meeting title.
This prompt guides you to summarize and export key information, instructions, and contextual details from a chat. It organizes the content into structured categories with dates, ensuring all relevant information is captured for easy sharing and review.
Summarize and export all important points, instructions, and contextual information exchanged in this chat, structured per your requirements. - Use section headers for each major category (e.g., Task Instructions, Preferences, System Guidelines, etc.). - For each entry within a category, list one entry per line, formatted as: [YYYY-MM-DD] - Entry content here. - Sort entries by oldest date first within each category. - If no date is known for an entry, use [unknown] instead of a date. - When preserving user content, use the original wording verbatim where possible, particularly for direct instructions, requirements, or preferences. - Wrap the entire export in a single code block (backticks, language unspecified) for easy copying. - After the code block, clearly state whether this is the complete set or if more entries remain. Persist in checking all prior conversation turns to ensure all relevant context is captured exhaustively. Think step-by-step to avoid missing any category or detail. ## Output Format: - The export must be wrapped in a single code block. - Use markdown section headers within the code block for each category. - Each entry in a category must be a single line, formatted as: [YYYY-MM-DD] - Entry content here. - If needed, use [unknown] if the date for an entry cannot be determined. - After the code block, add a plain text statement: "This is the complete set." or "More entries remain." (as appropriate). ## Example ``` # Task Instructions [2024-06-13] - I will move this chant to another AI agent to also support my projects. I want you to prepare detailed list of important points which were discussed in this chat. Please preapare. # Format Specifications [2024-06-13] - Use section headers for each category. Within each category, list one entry per line, sorted by oldest date first. Format each line as: [YYYY-MM-DD] - Entry content here. [2024-06-13] - If no date is known, use [unknown] instead. # Output Instructions [2024-06-13] - Wrap the entire export in a single code block for easy copying. [2024-06-13] - After the code block, state whether this is the complete set or if more remain. ``` (Real exports may be longer and contain more categories/entries as appropriate.) --- **Reminder:** Carefully review all prior turns to ensure nothing is missed, using verbatim wording for user requirements and instructions. Produce the export exactly as described above, including the final completeness statement.
