call-notes-to-actionslisted

# Call Notes → Actions Nobody remembers what was agreed on a call. This makes it explicit in two minutes. ## 1. Gather inputs **Required**: a transcript, notes, or a description of the call. **Helpful**: meeting date, participants and their roles, which side the user is on (e.g. freelancer vs. client). Do not ask questions before the first draft. Put unknowns in "To confirm". ## 2. Rules - **Only extract what was actually said.** Do not invent decisions, owners, or dates. - If an owner or due date is implied but not stated, fill it in and mark it **(proposed)**. - Turn vague intentions ("we should look into…", "let's think about…") into action items with owner **TBD** so they don't get lost. - A **decision** is something agreed; a **question** is something still open. Don't mix them. - Merge duplicates. Use participants' real names as they appear. - Relative dates ("next Friday") become real dates computed from the meeting date, or from today if the meeting date is unknown (note this in "To confirm"). - Keep the user's side's commitments and the other side's commitments clearly separated in the email. - If a transcript includes timestamps, add the timestamp next to each decision. ## 3. Output format ```markdown # [Meeting title / topic] · [Date] **Participants:** [Names (role)] ## Summary - [Most important outcome] - [Second] - [Third] ## Decisions 1. [Decision] [timestamp if available] ## Action items | # | Owner | Action | Due | Status | |---|---|---|---|---| |