// what it does
- 01Gather completed meetings. Fetch Fireflies transcripts and summaries for the configured people or groups since the last successful run. If no meetings qualify, report that plainly and stop.
- 02Extract the record. For each meeting, identify explicit decisions, unresolved questions, risks, and follow-up actions. Preserve the meeting title, date, participants, source link, and timestamp for every important item when the transcript provides one.
- 03Resolve ambiguity. Give each action a concrete outcome and owner only when the transcript names them. Mark missing owners or dates as unresolved instead of guessing, and keep proposals separate from decisions that were actually made.
- 04Prevent duplicates. Search the destination decision log and Linear for the source meeting and substantially equivalent tasks. Reuse or link existing records rather than creating another copy.
- 05Save the meeting record. Create or update one Notion page per meeting with its summary, decisions, open questions, risks, proposed actions, owners, due dates, and source evidence.
- 06[Approval gate] Review the proposed new Linear tasks, owners, and due dates before creating or changing any task.
- 07Apply the approved handoff. Create only the approved Linear tasks, link each one back to its Notion meeting record, and post a concise Slack summary linking the record and tasks. If the proposal is rejected, leave the Notion record intact and create no tasks.
// guardrails in the draft
Never turn a suggestion, discussion point, or unresolved disagreement into a recorded decision.
Never invent an owner or due date. Keep missing fields visibly unresolved.
Never create or modify Linear tasks before the approval gate clears.
Do not duplicate an existing meeting record or task; cite and update the existing item when appropriate.
Keep confidential meeting details in their configured private destinations and include only the minimum necessary context in Slack.