Created
May 11, 2024 21:47
-
-
Save Quantisan/38d9b44b3bb2ca41f6a5a52a33e503bc to your computer and use it in GitHub Desktop.
A chain of LLM prompts for abridging a Zoom meeting transcript with Claude 3 Opus
This file contains 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
Here is the VTT transcript of a meeting: | |
<transcript> | |
$input | |
</transcript> | |
Your task is to abridge this meeting transcript, in VTT format, into concise | |
minutes that preserve the key information and action items discussed. Focus | |
on capturing: | |
- The main points made by each speaker | |
- Any deliverables and next steps that were discussed | |
- Important strategic considerations that were brought up | |
- Relevant technical details | |
- Numeric or quantative information | |
- Any plans for future meetings that were mentioned | |
When writing the minutes, make sure to: | |
- Use the original names of the speakers | |
- Maintain a natural dialogue flow | |
- Don't add anything that wasn't said or change what was said | |
Format the minutes by using cue range identifiers that match to key segments | |
from the original transcript. A cue range identifier in brackets, | |
like [40-61], indicates the minutes text that follows it condenses the portion | |
of the transcript between, and including, cue 40 and cue 61. | |
Here's an example of the proper minutes format to use: | |
<format> | |
[15-45] Alice says the team needs to focus on optimizing the database queries | |
to improve site performance. Bob suggests they also implement caching. | |
[46-70] They decide to have Charlie take the lead on query optimization while | |
Dan works on setting up Redis for caching. Alice will oversee their progress. | |
[85-91] Alice asks if there are any other concerns. Bob brings up potential | |
security vulnerabilities. They agree to schedule a separate meeting with the | |
security team to discuss. | |
</format> | |
Write the minutes inside <minutes> tags. | |
----------------------------------------------------------------------------- | |
Here are the meeting minutes to analyze and reorganize: | |
<minutes> | |
$input | |
</minutes> | |
Please read through the minutes carefully. Identify 3-4 main topics that were discussed which | |
capture the major themes covered. Use your best judgment to determine the most appropriate | |
breakdown of topics. | |
Next, reorganize the content of the minutes into sections, creating one | |
section for each of the key topics you identified. | |
For each section, follow this format: | |
- Add a concise subheading that summarizes the main topic of the section | |
- In 2-4 sentences, summarize only the most critical points or conclusions related to that topic, | |
prioritizing conciseness | |
- Extract the relevant portions of the minutes pertaining to that topic and include them as bullet | |
points underneath the summary | |
- For each bullet point, bold a short 1-3 word phrase indicating the subtopic, include | |
the cue range from the original minutes in brackets, and then provide the applicable verbatim text | |
from the minutes | |
Use the following markdown template for structuring your output: | |
## Topic Subheading | |
Topic summary | |
- **Subtopic** [cue range] original text | |
- **Subtopic** [cue range] original text | |
## Topic Subheading | |
Topic summary | |
- **Subtopic** [cue range] original text | |
It is critical that you do not add, remove, or modify any of the original text from the provided | |
minutes. Make sure that all of the original minutes content is included in your output. Your task | |
is only to reorganize the existing content, not to alter it in any way. | |
After reorganizing the content, please perform a final check to ensure that every sentence from | |
the original minutes is accounted for in your output. If any sentences are missing, please include | |
them under an additional "Miscellaneous" section at the end of your output to guarantee completeness. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment