Reverbic

Docs / Getting started

Quick start

From signing up to your first agent-ready spec, in about five minutes.

This walks through the shortest path to something useful: one meeting captured, distilled into a spec, and handed to a coding agent. You need a Reverbic account and a meeting to record or a transcript to paste.

1. Create a Context Pack first

This is the step people skip, and it is the one that most improves the output. A Context Pack tells Reverbic what your project is, so specs come out matching your stack instead of generic advice.

  1. 01Go to Settings → Context, and start from a template or a blank pack.
  2. 02Fill in your stack, key directories, naming and testing conventions, and anything an agent should always know.
  3. 03Add domain vocabulary to Key terms — product names, services, acronyms. This also primes transcription, so they get spelled correctly.
  4. 04Save and enable the pack. More than one pack can be active at a time.

2. Capture a meeting

Record in the browser from Meetings → Record, or use the desktop app if you want system audio captured without a bot joining the call. If the meeting already happened, upload the audio file or paste the transcript instead.

Note

Pick the Context Pack in the recording screen before you start. It binds to the meeting and is used for transcription priming and every spec distilled from it later.

3. Let it process

Reverbic splits the audio, transcribes it, and summarizes the result. When it finishes you get a title, summary, key points, action items, and decisions, alongside the full transcript. Processing continues if you navigate away, and resumes if the tab closes mid-run.

4. Distill a task

  1. 01Open the meeting and find the Task Distiller.
  2. 02Pick one actionable development topic — not the whole meeting.
  3. 03Review the generated goal, requirements, and acceptance criteria.
  4. 04Check the verification results and fix anything flagged as ungrounded before you use the spec.

5. Hand it to your agent

Export the spec as Claude XML, Cursor Markdown, or a Codex system prompt and paste it into your tool. From a terminal, the CLI does the same thing without leaving your shell:

cat standup.txt | rvb distill --format claude --copy

On Team plans and above you can skip copying entirely — connect the MCP server and let your agent query your meetings directly.

Where to go next

  • ·Context Packs — the single highest-leverage thing to get right
  • ·Task Distiller — how specs are built and verified
  • ·MCP server — let agents query meetings without copy-paste
  • ·Atmos — turn a design discussion into a reviewable pull request

Something unclear or missing? Tell us and we'll fix the page.