Investor Update Writer

What it takes in

The inputs you provide on each run, validated before anything executes.

2 tasks, run in order.

Each task passes its result to the next. Here's what each does and what it produces.

1. 01
   Structure the update. From {{metrics}} and {{highlights}}, build the skeleton of the investor update: a TL;DR of 2 to 3 sentences capturing the month's headline; a metrics section stating each metric plainly with its month-over-month movement (up, down, or flat, and by how much): flag any metric that lacks a comparison point rather than inventing one; a wins section with the strongest highlights; a challenges section stating lowlights honestly and without spin, including what is being done about each; and a specific asks section drawn from {{asks}} if provided: sharpen each ask into something an investor can act on. Do not fabricate numbers or events not present in the inputs. Present this as a readable structured draft, never JSON.

   Expected output

   A readable structured draft using headings and bullets, with no JSON and no code blocks: TL;DR (2 to 3 sentences), Metrics (each metric with its month-over-month movement stated plainly, with a flag on any metric missing a comparison point), Wins (bullets), Challenges (bullets stated honestly, each with what is being done about it), and Asks (specific, actionable bullets, or a note that no asks were provided).
2. 02
   Write the final email. Using the structured draft from Task 1, write the ready-to-send investor update email in a founder voice: confident, honest, and concise, readable in under three minutes. Include a subject line, a one-line opener, the TL;DR, the metrics with movement, wins, challenges, and asks, and a brief sign-off. Then write a separate 3-line version for investors who skim: the headline number, the most important development, and the single most important ask. Do not add facts, numbers, or spin not grounded in Task 1. Present as readable, ready-to-send copy, never JSON.

   Expected output

   A readable, ready-to-send section with no JSON and no code blocks: Subject Line; Full Update (the complete email in a confident, honest, concise founder voice with TL;DR, metrics, wins, challenges, asks, and sign-off); and 3-Line Skim Version (exactly three lines: headline number, most important development, most important ask).