Founder Debrief

Extract structured insights from founder conversations (investor pitches, customer discovery, partner meetings, advisor calls) and route them to the right canonical files so nothing gets lost and positioning compounds over time.

Most founders leave conversations with scattered notes or nothing at all. This skill turns every conversation into a system update - capturing exact phrases that resonated, objections that need answers, and positioning drift before it becomes a problem.

Before Starting

1. Check if the user has a canonical file system set up. Look for files like canonical/talk-tracks.md, canonical/objections.md, or similar in the project directory.
2. If no canonical files exist, ask: "You don't have canonical files set up yet. Want me to create the starter set? (See references/canonical-files.md for what each file does.)"
3. If canonical files exist, read them so you can route new insights correctly and avoid duplicating what's already captured.

When to Use

• After any conversation with an investor, customer, design partner, advisor, or industry contact
• When the user pastes meeting notes and wants them processed
• When the user describes a conversation from memory
• During batch processing of multiple conversation notes
• Any time the user says "debrief" or asks to extract insights from a conversation