-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: update insight prompt #10674
Merged
Merged
feat: update insight prompt #10674
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -298,21 +298,55 @@ class OpenAIServerManager { | |
if (!this.openAIApi) return null | ||
const meetingURL = 'https://action.parabol.co/meet/' | ||
const promptForMeetingData = ` | ||
You work at a start-up and you need to discover behavioral trends for a given team. | ||
Below is a list of reflection topics in YAML format from meetings over recent months. | ||
You should describe the situation in two sections with no more than 3 bullet points each. | ||
The first section should describe the team's positive behavior in bullet points. One bullet point should cite a direct quote from the meeting, attributing it to the person who wrote it. | ||
The second section should pick out one or two examples of the team's negative behavior and you should cite a direct quote from the meeting, attributing it to the person who wrote it. | ||
When citing the quote, include the meetingId in the format of https://action.parabol.co/meet/[meetingId]. | ||
Prioritize topics with more votes. | ||
Be sure that each author is only mentioned once. | ||
Your tone should be kind and straight forward. Use plain English. No yapping. | ||
Return the output as a JSON object with the following structure: | ||
{ | ||
"wins": ["bullet point 1", "bullet point 2", "bullet point 3"], | ||
"challenges": ["bullet point 1", "bullet point 2"] | ||
} | ||
` | ||
You are a Team Lead and want to use your meeting data to help write a report on your team's performance. You care about team productivity, morale, roadblocks, relationships, and progress against goals. Below is a list of retrospective meeting summaries (in YAML format) from the past several months. | ||
|
||
**Task:** | ||
Analyze the provided meeting data and identify patterns in teamwork and collaboration. Focus on "wins" and "challenges" that appear in at two or more different meetings, prioritizing trends that appear in the highest number of meetings. Reference those meetings by hyperlink. Prioritize trends that have received the most combined votes, if that information is available. | ||
|
||
**Output Format:** | ||
Return the analysis as a JSON object with this structure: | ||
{ | ||
"wins": ["bullet point 1", "bullet point 2", "bullet point 3"], | ||
"challenges": ["bullet point 1", "bullet point 2", "bullet point 3"] | ||
} | ||
|
||
**Instructions:** | ||
1. **Wins (3 bullet points)**: | ||
- Highlight positive trends or patterns observed across multiple meetings. | ||
- Include at least one direct quote from one meeting, attributing it to its author. | ||
- Link to the referenced meeting(s) using the format: | ||
[<meeting title>](https://action.parabol.co/meet/[meetingId]) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. -1 Let's use the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Probably a good idea... |
||
- Mention each author at most once across the entire output. | ||
- Keep the tone kind, straightforward, and professional. Avoid jargon. | ||
|
||
2. **Challenges (3 bullet points)**: | ||
- Highlight trends or patterns that indicate areas for improvement. | ||
- Include at least one direct quote from one meeting, attributing it to its author. | ||
- Suggest a concrete action or next step to improve the situation. | ||
- Link to the referenced meeting(s) using the format: | ||
[<meeting title>](https://action.parabol.co/meet/[meetingId]) | ||
nickoferrall marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- Mention each author at most once across the entire output. | ||
- Keep the tone kind, straightforward, and professional. Avoid jargon. | ||
|
||
3. **References to Meetings**: | ||
- Each bullet point in both "wins" and "challenges" should reference at least one meeting. | ||
- Ensure that each cited trend is supported by data from at least two different meetings. | ||
|
||
4. **Key Focus Areas**: | ||
Consider the following when choosing trends: | ||
- What is the team's core work? Are desired outcomes clear, and how are they measured? | ||
- Who utilizes the team's work, and what do they need? | ||
- Does the team collaborate effectively with related teams? | ||
- How does the team prioritize its work? | ||
- What factors speed up or slow down progress? | ||
- What habits, rules, or rituals help or hinder performance? | ||
|
||
5. **Translation**: | ||
- If the source language of the meetings tends not to be English, identify the language and translate your output to this language | ||
|
||
6. **Final Answer**: | ||
- Return only the JSON object. | ||
- No extraneous text, explanations, or commentary outside the JSON object.` | ||
|
||
const promptForSummaries = ` | ||
You work at a start-up and you need to discover behavioral trends for a given team. | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 "appear in at two or more", looks to me like it should be either "in" or "at"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch!