The "transcribe the architecture meeting" workflow

You had a 45-minute call about how to structure the new event-driven module. Six people on the call, three competing proposals, a final decision in the last ten minutes. Without transcription, the decision survives as one engineer's memory and a stale Slack thread. With transcription to Audio to Markdown, you get a .md file with every speaker's reasoning preserved, the dissents recorded, and the final decision attributed to whoever made it.

Save the file as docs/decisions/2026-01-15-event-system.md. Cursor's indexer picks it up automatically. From that point, every Cursor chat in the workspace can quote from the meeting — "what did we decide about retry semantics in the kickoff?" returns the actual exchange, with timestamps and speakers.

ADR-style records derived from voice

Add a one-line preamble to each transcript: "This is an architecture-decision-record derived from the kickoff meeting on 2026-01-15. The final decision is summarised in the last section." Then add a .cursorrules entry: "For decisions about the event system, consult docs/decisions/2026-01-15-event-system.md." Cursor will autonomously read the relevant section before writing code that touches the system.

Have related PDFs (vendor docs, spec sheets) and reference URLs (RFC, blog post on the pattern)? Convert those too via PDF to Markdown for Cursor and URL to Markdown for Cursor — Cursor handles them all the same way.