← All guides

Walking a task back to its meeting

A task on its own is a sentence. A task with the five minutes of conversation that produced it is a spec. Here's the shape of prompt that reliably gets the second one.

Why the meeting matters

Onvoi extracts action items with provenance: every task remembers the meeting, the segment, and often the speaker it came from. That link is what lets a connected tool answer questions the task text never contained — who objected, what the deadline actually depends on, which of two interpretations the room settled on.

Your tool doesn't need to be told how to do this. The connection playbook ships at connect time, so an instruction as loose as “pick up my next task and do it properly” already walks the chain.

TipName the meeting loosely — “my last call with Northwind” resolves fine. Exact titles and IDs are never required.

The prompt

Three clauses: what to pick up, how deep to read, where to put the result.

claude code — prompt
Take my oldest open task on the Northwind project.
# read the source, not just the title
Read the meeting it came from and the decisions
around it, then write the implementation spec.
# put the work back where the team will find it
Save it to the project as a file and mark the
task in review.

What comes back

  • A spec that cites the decision it implements, not a restatement of the task title.
  • Open questions the room never resolved, listed rather than invented.
  • A file attached to the project, and task status rolled up into project progress.
CarefulA connected tool can complete tasks. If you'd rather review first, say “mark it in review” — as above — instead of “mark it done”.