Meeting to audio briefing
in one command.

Give it a transcript and it does everything: gathers project context, runs a strategic analysis grounded in your CLAUDE.md, docs, and git history, generates a TTS-optimized voice text, produces an MP3, and drops it in your Dropbox. Listen to the briefing on the drive home.

Get the Skill Voice Kit Setup

Also available in ai-voice-kit.

/voice-to-text transcript /voice-briefing analysis + voice text + audio.mp3

The full chain, one command

Combines strategic analysis and text-to-voice into a single workflow. Reads your project context, analyzes the transcript with product-aware intelligence, converts the analysis to speech-friendly text, generates an MP3, and copies it to Dropbox. You get a written analysis AND an audio briefing.

  • Project-aware analysis (reads CLAUDE.md, docs, git log)
  • Identifies participants from transcript
  • Cross-references competitors with existing intel
  • Produces analysis.md + analysis-voice.txt + analysis-audio.mp3
  • Auto-copies to Dropbox for mobile listening
  • Works after /voice-to-text or with any transcript
> /voice-briefing transcript.md Gathering project context... .claude/CLAUDE.md — product stage git log — 12 commits this week docs/private/ — competitor analysis Analyzing transcript... 2 participants identified Mode: Consulting engagement Generating audio briefing... Output: └── analysis.md (written) ├── analysis-voice.txt (TTS-ready) └── analysis-audio.mp3 (6m 18s) Dropbox: └── Voice Files Work/ Client Call - analysis.mp3

Three files, one workflow

The written analysis (analysis.md) is a full strategic breakdown. The voice text (analysis-voice.txt) strips markdown and adds spoken cues. The audio (analysis-audio.mp3) is the voice text converted to speech, ready for your commute.

analysis.md (written) └── Product Context (auto-gathered) ├── Comprehensive Summary ├── Strategic Analysis └── Win Probability ├── Feature-by-Feature Fit ├── Development Velocity └── Strategic Angles ├── The Hard Truths └── Competitive Landscape ├── Red Flags └── Next Actions └── Roadmap Impact Assessment analysis-voice.txt (TTS-optimized) Markdown stripped, tables → prose, acronyms expanded, spoken transitions. "Now let's move to the hard truths..." analysis-audio.mp3 Kokoro TTS, am_michael voice 6m 18s, 5.2 MB

Grounded in what you know

The analysis is only as good as the context. The skill reads everything available — CLAUDE.md for product state, git log for development velocity, docs for competitor intel, and memory for prior conversations. The result is advice grounded in reality, not generic strategy.

  • .claude/CLAUDE.md — product identity, stage, roadmap, milestones
  • git log — recent commits, development velocity, what just shipped
  • docs/private/ — competitor analysis, strategic documents
  • notes/ — prior meeting summaries, strategy sessions
  • memory/ — persistent context from prior conversations