Use Case #8: Voice Notes to Specs

I have ideas in the car. Used to lose them. Now I record everything.

The problem: my voice notes are chaos. Half-sentences, corrections, tangents, "actually no wait" reversals.

The Workflow

1. Record voice memo while driving
2. Transcribe (Whisper or Otter)
3. Paste the mess into Claude
4. Get clean specs out

Example

My input: "so I'm thinking about the onboarding flow and like... the thing is people get confused about... wait no actually the real problem is they don't know what to do first. So maybe we need like a checklist or... hmm... or maybe more like a progress thing? You know what I mean?"

Claude's output: A structured markdown document with Problem Statement, Proposed Solution, Requirements (progress indicator, next action clarity, skip functionality), Open Questions, and Acceptance Criteria.

What Makes This Work

Intent extraction. Claude understood that "you know what I mean" and "those things that show you" meant progress indicators. It filled in my gaps.

Contradiction handling. I said "maybe skip" then "wait that might be confusing." Claude captured both as a design tension to resolve, not a contradiction to ignore.

Structure imposition. My rambling became sections: Problem, Solution, Requirements, Questions, Criteria.

The Pattern

"Here's a voice note transcript about [feature/problem]. Turn this into a technical spec with requirements and acceptance criteria."

No cleaning needed. The messier the better - Claude works with raw thought.

Try It Yourself

Copy this to turn your voice notes into specs:

I have a voice note transcript to convert into a technical spec.

**Context:**
1. What's this about? (new feature / bug fix / improvement / idea)
2. What project does this relate to?
3. What output format? (technical spec / user story / PRD / requirements list)

Paste your transcript below (don't clean it up - raw is better).

I will:
- Extract the core intent from your rambling
- Identify requirements (even implicit ones)
- Capture design tensions and open questions
- Structure everything into a proper spec
- Add acceptance criteria
- Flag anything that needs clarification

Just paste the transcript and I'll handle the rest.

I do this 3-4 times per week. Hundreds of features have started as car rambles.