Turn meeting notes into Linear or Jira tickets
Cursor reads meeting notes and drafts tasks for Linear or Jira with title, description, and acceptance criteria.
A set of tickets ready to create: each with a title, a description, and what done looks like.
- 1
Clean the notes once
Remove side conversations and jokes. The agent should see only the decisions.
- 2
Review every ticket
Read the title and acceptance criteria. Reject any ticket that was not agreed to in the room.
- 3
Create the tickets in batch
Paste them into Linear or Jira. Do not ask Cursor to create them via API unless you already have that wired.
The prompt to paste
Turn these meeting notes into tasks for [Linear/Jira]. Read the notes and create tickets for work that was agreed to. Meeting notes: [paste] For each task return: - Title: starts with a verb, under 60 characters - Description: what needs to be done and why, under 200 words - Acceptance criteria: 2-4 lines, each starting with "User can..." or "System should..." - Labels: from [your team's label list], or suggest new ones if none fit Rules: - Only create tasks for work the room agreed to. If it was only discussed, skip it. - If the notes do not say who owns a task, leave the assignee blank. - Do not add deadlines unless a date was mentioned in the meeting. - Do not split one decision into multiple tickets unless the work actually has separate outcomes. If the notes are ambiguous, mark that task "needs clarity" and say what is missing.
A suggestion is not a task. If the room did not commit, do not create the ticket.
Sample case written by Hidden Logic Lab. Not affiliated with Cursor.
More in Operations
Get new cases in your inbox
Weekly notes on new use cases and agent workflows. No product pitches.