/tldr -- Conversation Summary to Notes

When invoked, follow these steps exactly:

Step 1: Summarize the conversation

Look at the last 5-10 back-and-forths in the current conversation. Write a TLDR that captures the substance of what was discussed, not just a log of actions taken.

The note should be useful to someone (including your future self) who wasn't in the conversation. They should be able to read it and understand the ideas, decisions, and reasoning -- not just "we did X, Y, Z."

Structure the summary into these sections:

• Key ideas and content -- The actual substance. If you discussed a video structure, include the structure. If you brainstormed titles, include the top candidates and why. If you designed an architecture, describe it. This is the most important section -- preserve the thinking, not just the actions.
• Decisions made -- What was decided and why. Include the reasoning, not just the conclusion.
• Actions taken -- Files created, commands run, things built. Keep this part brief -- just a reference list.
• Open threads -- Anything left unfinished or flagged for later.

The key ideas section should be the longest. Be specific -- include names, numbers, structures, frameworks, exact titles, quotes, timestamps. If you spent 20 minutes working through a video script structure, the TLDR should contain that structure, not just "discussed video structure."