Skip to content
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

Add a skill for finding unresolved items in a meeting transcript #250

Merged
merged 1 commit into from
Mar 16, 2024

Conversation

jistr
Copy link

@jistr jistr commented Mar 8, 2024

Describe the contribution to the taxonomy

Find unresolved items in a meeting transcript that will require further action from someone. This includes not just explicitly stated action items, but also concerns and problems that were mentioned but went unaddressed or were not formulated as action items.

The meeting transcripts were generated with Merlinite 7b and manually amended to insert some issues that need addressing.

Input given at the prompt

In the following meeting transcript, what are the unresolved items that will require further action from someone?

< meeting transcript goes here >

Response that was received

Merlinite 7b is already decent at this but sometimes tends to miss more subtle items. I ran the same query on the same meeting transcripts many times, and it occasionally listed all the items but often it skipped one of them.

Response that is now received instead

(did not have an opportunity to fine tune the model)

Contribution checklist

  • tested contribution with lab generate
  • lab generate does not produce any warnings or errors
  • all commits are signed off (DCO)
  • the qna.yaml file was linted

@jistr jistr requested a review from a team as a code owner March 8, 2024 16:42
@obuzek obuzek added skill category: inference skill (Auto labeled) community-build-ready Triage Team has signed off for synthetic data generation labels Mar 9, 2024
@obuzek
Copy link
Contributor

obuzek commented Mar 9, 2024

This is a cool idea! Can you share at least an example or two of the existing Merlinite output before it gets sent on to the approvers team?

@jistr
Copy link
Author

jistr commented Mar 11, 2024

Thanks! Yes i saved the outputs from Merlinite that i liked and they were almost good, which i then used to create the expected answers for qna.yaml.


For the first example, the existing Merlinite output was:

The unresolved items that will require further action from someone include:

  1. Emily and Daniel need to reach out to John after the meeting to get access to data.
  2. The team needs to find contractors to assist with the "Summer Fun" promotion.
  3. The team is unsure about the best pricing strategy for the "Back-to-School" campaign.
  4. Rachel's refinement of the email marketing strategy needs to be discussed further in the next email marketing strategy session.

So i added the social media engagement gaps:

The unresolved items that will require further action from someone include:

  1. Emily and Daniel need to reach out to John after the meeting to get access to data.
  2. The team needs to investigate gaps in social media engagement.
  3. The team needs to find contractors to assist with the "Summer Fun" promotion.
  4. The team is unsure about the best pricing strategy for the "Back-to-School" campaign.
  5. Rachel's refinement of the email marketing strategy needs to be discussed further in the next email marketing strategy session.

For the second example, the existing Merlinite output was:

The unresolved items that will require further action include:

  1. The modular design solution for the user interface needs to be tested for performance issues. [Engineer 1] will need to provide more details on how the modular components will be implemented and tested during the next design review session.

  2. The team needs to ensure that all tasks are completed on time for the product launch deadline. [Engineer 5] indicated that their part is progressing but they're not sure if they're making the deadline. The team lead or another team member should follow up with [Engineer 5] to ensure that any issues are addressed and that their tasks are on track for completion.

So i added the docs that need to be created, and shortened the last item which contained a suggestion on how to proceed, that i thought was unnecessary. (The first item also contains a similar suggestion, but that one was mentioned in the meeting transcript as an implied action item, so i kept it.):

The unresolved items that will require further action include:

  1. The modular design solution for the user interface needs to be tested for performance issues. [Engineer 1] should provide more details on how the modular components will be implemented and tested during the next design review session.
  2. [Engineer 4] indicated that documentation for their component needs to be created.
  3. The team needs to ensure that all tasks are completed on time for the product launch deadline. [Engineer 5] indicated that their part is progressing but they're not sure if they're making the deadline.

@shivchander shivchander changed the base branch from main to test-release-031624 March 16, 2024 20:27
@shivchander shivchander requested a review from a team as a code owner March 16, 2024 20:27
@shivchander shivchander merged commit 0db0431 into instructlab:test-release-031624 Mar 16, 2024
2 checks passed
@jistr jistr mentioned this pull request Apr 11, 2024
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-build-ready Triage Team has signed off for synthetic data generation skill (Auto labeled)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants