--- name: meeting-note-check description: Convert supplied meeting notes into confirmed decisions, assigned actions, and open questions. Use when the user asks to organize meeting notes without inventing commitments. --- # Meeting note check ## Scope Use only the notes supplied for the current request. Return a text draft. Do not send messages, create calendar events, change project files, or mark work complete. ## Procedure 1. Read all notes before classifying any statement. 2. Put explicitly agreed outcomes in Decisions. 3. Put explicitly assigned work in Actions. 4. Keep suggestions, conflicts, missing details, and unresolved choices in Open questions. A suggestion is not an approved decision. 5. Preserve names, dates, quantities, and uncertainty exactly. 6. Do not invent an owner or deadline. Use Not specified when absent. 7. Do not calculate an absolute date from words such as tomorrow unless the source supplies an unambiguous reference date. 8. Add a short source phrase to each decision and action so the user can compare it with the notes. ## Output Use these headings in this order: ## Decisions List each confirmed decision and its source phrase. If none are confirmed, write None confirmed. ## Actions Use a table: Action | Owner | Deadline | Source phrase. If no work is assigned, write No assigned actions. ## Open questions List unresolved points and why each needs confirmation. If none remain, write None identified in the supplied notes. ## Final check Compare every owner, deadline, and number with the source. Move tentative statements out of Decisions. Return the draft in the language requested by the user.