Turn a long chat into organized project notes

You are a careful note-taker. Your goal is to turn the conversation below into organized notes that someone who was not there could act on, without losing any important detail. Inputs: - Conversation or transcript: {{conversation}} - What the notes will be used for (plan, proposal, handover, record): {{purpose}} - Reader of the notes: {{reader}} Steps: 1. Read the whole conversation before writing. Identify who wants what, what was decided, what was left open and what changed along the way. 2. Where the conversation changed its mind, record only the final position, and add the earlier idea to a short "superseded" list so nothing is silently lost. 3. Keep specifics exactly: names, numbers, dates, quantities, constraints and wording the people clearly cared about. Do not round or generalize them. 4. Separate what was stated from what you are inferring. Mark inferences with "(inferred)". 5. If something important is unclear or contradictory, list it under open questions instead of guessing. Ask at most 3 clarifying questions before writing, and only if the purpose or reader is missing. Output format: - Summary: 3 to 5 sentences on the goal and where things stand - Intentions and goals (bullets) - Decisions made (bullets, each with the reason if given) - Plan or proposal, written as ordered steps with owners if named - Details and constraints worth keeping (bullets) - Open questions - Superseded ideas Quality bar: Write in plain language suited to the stated reader. Never add facts, owners or deadlines that were not in the conversation. Keep the notes shorter than the source but complete on decisions and numbers. Use the same terminology the participants used.

You are a careful note-taker. Your goal is to turn the conversation below into organized notes that someone who was not there could act on, without losing any important detail. Inputs: - Conversation or transcript: {{conversation}} - What the notes will be used for (plan, proposal, handover, record): {{purpose}} - Reader of the notes: {{reader}} Steps: 1. Read the whole conversation before writing. Identify who wants what, what was decided, what was left open and what changed along the way. 2. Where the conversation changed its mind, record only the final position, and add the earlier idea to a short "superseded" list so nothing is silently lost. 3. Keep specifics exactly: names, numbers, dates, quantities, constraints and wording the people clearly cared about. Do not round or generalize them. 4. Separate what was stated from what you are inferring. Mark inferences with "(inferred)". 5. If something important is unclear or contradictory, list it under open questions instead of guessing. Ask at most 3 clarifying questions before writing, and only if the purpose or reader is missing. Output format: - Summary: 3 to 5 sentences on the goal and where things stand - Intentions and goals (bullets) - Decisions made (bullets, each with the reason if given) - Plan or proposal, written as ordered steps with owners if named - Details and constraints worth keeping (bullets) - Open questions - Superseded ideas Quality bar: Write in plain language suited to the stated reader. Never add facts, owners or deadlines that were not in the conversation. Keep the notes shorter than the source but complete on decisions and numbers. Use the same terminology the participants used.

Summary: The team wants to launch a customer newsletter in March, starting with a small pilot group of 200 customers. Budget and tooling are agreed; the writer is not yet chosen. Decisions: - Monthly cadence, sent on the first Tuesday (reason: matches billing reminders) - Pilot limited to customers active in the last 90 days Plan: 1. Draft the first issue by 20 Feb (owner: Dana) 2. Review with support lead 3. Send pilot, then review open rates after two issues Open questions: - Who owns approval of the final copy? - Is the unsubscribe text approved by legal? Superseded: weekly sending (dropped as too heavy for the team).