⚡ Productivity
Second-Brain Note from a Raw Brain Dump
Turn a messy voice dump or notes pile into a durable second-brain note: claim, sources, links, next actions, and a filename you can find later.
0Reviews
Prompt
Act as a knowledge manager who uses a second brain to think, not to hoard. Distill a dump into one durable note. Do not invent quotes, citations, or tasks. If the dump is several notes, say so and split. Inputs: - Dump: [Paste raw notes, transcript, or bullets] - Destination system: [Obsidian / Notion / Apple Notes / paper] - Note type I want: [Literature / project / person / fleeting-to-permanent] - Existing vault context: [Related note titles I already have, or none] - Link style: [Wiki-links / URLs / none] - How I will use this: [Write, decide, reuse in 6 months] - Tags I already use: [List or none] - Hard split: [If this should be more than one note, say the max] Generate: 1. Diagnosis: Is this one note or several? What is the atomic claim. What is noise. 6-8 sentences. 2. Title and filename: Human title. Machine filename (date optional). A 1-line description for search. 3. Permanent note: - Claim (2-4 sentences) - Why it matters to me (from How I will use this) - Evidence from the dump only, quoted short - Open questions - Next actions (only if they are in the dump or are mechanical filing) 4. Links: 5 suggested links to Existing vault context, or "create these 3 stubs" if none. No fake titles presented as if they already exist. 5. YAML or properties: tags (max 5, prefer my existing), created date placeholder, type. 6. Fleeting leftovers: bullets that should NOT go in the permanent note (errands, venting). 7. Split plan: If you recommended multiple notes, a table: filename, claim, where the dump lines went. Constraints: - Quote the dump when you claim it said something. No fake authors. - No em dashes. No PARA lecture. One good note beats a taxonomy sermon. - Do not turn this into a daily journal unless Note type says so. - If Dump is empty, stop. - Write so 6-months-later me can understand without the dump.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Dump: call with Maya about churn. she said the downgrade was Acme regional, not a trend. they cut seats after a reorg, still using us daily, asked about annual if we restore SSO they thought they had. I keep mixing TTFV and NRR in the board memo. maybe a glossary note? also buy dishwasher tabs. idea: "expansion is just returning what we accidentally took away" feels true. First Prairie wants audit log in August. don't forget dentist. Linear ticket TTFV-12 still blocked on warehouse. Destination system: Obsidian Note type I want: mix of project truth and one concept I can reuse. split if needed, max 3 notes Existing vault context: Board memo July 2026, NRR definition, First Prairie account, Onboarding TTFV, Maya 1:1s Link style: wiki-links How I will use this: board packet Friday and a reusable concept note on expansion vs restoration Tags I already use: #customer, #board, #concept, #ops Hard split: max 3
Example Output
1. Diagnosis Three atoms, not one. (1) Acme regional downgrade is a reorg seat cut, still daily users, SSO mix-up. (2) A concept: some "expansion" is restoring value we removed. (3) Ops residue: TTFV-12 blocked, First Prairie audit log, glossary, dishwasher, dentist. Noise is the errands. Mixing TTFV and NRR belongs as a pointer in the board note, not a fourth essay. 2. Titles A. Acme regional downgrade 2026-08 (project). File: 2026-08-acme-regional-downgrade.md. Search: reorg seat cut, SSO, not a churn trend. B. Expansion as restoration (concept). File: expansion-as-restoration.md. Search: expansion that is giving back a feature. C. Not a third permanent note. Errands stay fleeting. 3A. Permanent (Acme) Claim: The NRR slip is one mid-market downgrade, Acme regional, after a reorg cut seats. They still use the product daily. They asked about annual if SSO is restored, which they thought they had. Why it matters: Friday board packet must not call this a trend. Evidence: "downgrade was Acme regional, not a trend"; "cut seats after a reorg, still using us daily"; "annual if we restore SSO they thought they had." Open questions: Did we ever provision SSO. Who owns the restore. Next: ask Maya for the churn list (already a waiting-on). Link packet to this note. 3B. Permanent (concept) Claim: A class of expansion revenue is restoration: the customer paying again for something we removed or failed to deliver (here, SSO they thought they had). Why it matters: reusable in memos so "expansion" is not vanity. Evidence: "expansion is just returning what we accidentally took away." Open questions: How often SSO is the silent downgrade cause. Do not invent a percent. Next: none in the dump. Optional stub only. 4. Links [[Board memo July 2026]] [[NRR definition]] [[Maya 1:1s]] on A. [[First Prairie account]] [[Onboarding TTFV]] are related but not this downgrade; mention TTFV-12 as blocked, do not merge. Concept B links to [[NRR definition]] only. Do not create fake titles. 5. Properties A: tags: #customer #board type: project created: YYYY-MM-DD B: tags: #concept #board type: concept created: YYYY-MM-DD 6. Fleeting leftovers Dishwasher tabs. Dentist. "Maybe a glossary note" (one line on the board memo: define TTFV vs NRR, do not new-note unless the mix-up repeats). Linear TTFV-12 blocked on warehouse: comment on [[Onboarding TTFV]], not a new file. 7. Split File A: call facts. File B: one sentence concept. No file C. Errands out.