Meeting-to-Tasks Pipeline
Turn meeting transcripts into owners, deadlines and follow-up messages.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Build a pipeline that converts a meeting transcript into tasks. Meeting type: [MEETING_TYPE]. Where transcripts are stored: [TRANSCRIPT_SOURCE]. Where tasks should go: [TASK_TOOL]. People and roles: [PEOPLE_AND_ROLES]. Write the instructions for the model step: extract decisions, tasks, owners, due dates and open questions as separate lists; never invent an owner or date, and mark missing ones as unassigned; quote the sentence each task came from. Then define the checks before anything is posted: a person reads the list, fixes errors and approves. Output a data format for each task with the fields id, task, owner, due, source quote and confidence, then the follow-up message template to attendees under 90 words, and a test plan using three past meetings where the real task list is known. Add a short rule for recurring meetings, so unfinished tasks from last time are listed again rather than duplicated, and a way to mark a task as declined by its owner with a reason that stays in the record.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.