Task Distiller

The Task Distiller finds development topics in a meeting and turns the one you pick into a focused, structured spec. It is deliberately not a summarizer: a summary tells you what a meeting was about, a spec tells an engineer or an agent what to build.

What a spec contains

Goal

The thing that needs to be built, fixed, or changed.

Context

Relevant project background, enriched from the active Context Pack.

Requirements

The concrete behaviors and constraints that were agreed.

Acceptance criteria

The conditions that define done.

Verification

Generating a spec from a transcript with a language model creates an obvious risk: the model can make a plausible detail sound like a decided detail. So a separate pass checks the result.

• ·Each requirement is checked against the transcript, and anything with no basis in what was said is flagged
• ·The spec is scored for specificity, completeness, and actionability
• ·Relevant technology or conventions from the active Context Pack that are missing get surfaced

Exports

A finished spec can be copied in the shape your tool expects — structured XML for Claude, Markdown for Cursor, or a system-prompt-style brief for Codex — or opened directly in Claude.

Supplementing a spec

If a meeting was light on detail, you can supply extra material — notes, a doc, a thread — and re-distill against it. Supplemented tasks persist with the meeting.

From the terminal

The same distillation runs from the CLI over a file or piped text:

rvb distill ./standup.txt --format claude --copy

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