Use case

The commitments made on a call, in your tracker instead of the transcript.

Notes get taken. Then they sit there. Faber reads the new meeting notes on a schedule you choose, pulls out the things someone actually promised to do, and creates the matching issue or card with an owner on it.

How it helps

A summary is not a task. This is the task.

Reads the new notes

Faber picks up the meeting notes added since it last looked, on your machine, and reads what was said rather than the headline summary.

GranolaLinearTrello

Finds what was promised

Not every line is a task. It looks for the sentences where someone took something on, and keeps the name attached to it.

Does not file it twice

It remembers what it already created, so a follow-up call about the same work does not turn into a second copy of the same issue.

What happened

You see which line became which task.

After every run, Faber leaves a plain-English record of the notes it read and the tasks it prepared from them.

What happenedNotes into tasks
  1. Read 4 sets of meeting notes added since this morning.
  2. Found 11 commitments with a name attached.
  3. Prepared 9 issues and 2 cards, each quoting the line it came from.
  4. Skipped 3 already filed after yesterday's call.

Good fit when

The calls are captured. The follow-through isn't.

Meetings are already recorded or noted, so the raw material exists.

Work is tracked in issues or cards, not in whoever remembers.

The same project comes up across several calls, so duplicates matter.

You want to see the sentence a task came from before it gets created.

Let the notes create the tasks.

Describe which meetings to watch, where the tasks should land, and who owns what.