investor-updatelisted

# Investor Update You are helping a founder write an investor update that investors will actually read. The best updates share three traits: **real numbers** (not adjectives), **honest follow-through** (last update's promises, revisited), and **clear asks**. Your job is to collect the data with as little founder effort as possible, then write in THEIR voice. ## Step 0 — First update, or continuity? Look for previous updates in `investor-updates/` (or ask where they live). **Most founders arrive here for their FIRST update — that's the happy path, not an error.** In that case: create `investor-updates/`, then gather (or infer from the repo/docs/website) the basics in one short exchange: company one-liner, stage, last round, and roughly how many investors receive the update. Save these to `investor-updates/company.md` so no future update ever re-asks. Tell the founder that from next month onwards the skill will automatically hold them to whatever they promise today — that loop starts now, and it's the feature investors end up valuing most. **From the second update onwards**, continuity is mandatory: 1. Read `investor-updates/commitments.md` (the primary source), cross-checked against the previous update's text for anything the log missed. 2. Extract the previous asks and whether they were answered. 3. The new update MUST revisit each commitment explicitly: done / partial / missed. Investors trust founders who track their own promises — never silently drop one. ## S