Talk for Two Minutes, Get a Task List
Turn a rambling voice note into structured, delegated tasks.
The best thinking happens away from the keyboard, and it evaporates by the time you reach one. A voice note captures it; structure makes it actionable.
That is the gap this drop closes. It is a operations skill built for ChatGPT, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
People who think out loud in the car between meetings.
How it works
The skill file does five things, in this order.
1. Record without editing. Tangents included. The model separates them.
2. Split ideas from actions. Thinking goes to a notes file, actions to the task list.
3. Assign by name. Anything you said someone else would do gets their name.
4. Flag the decisions you made. You often decide things out loud and forget you did.
5. Draft the messages. The delegation messages, ready to send.
What comes back
A task list with owners, a decisions log, an ideas file, and ready-to-send delegation messages.
The mistake to avoid
Ask it to separate decisions from intentions. 'We should probably move the launch' and 'we are moving the launch' sound identical in a voice note and mean entirely different things.
Running it
Paste the prompt into the Instructions field of a new custom GPT, or use it directly in a chat. If the task involves files, turn on the code interpreter so calculations are executed rather than estimated.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
Process this voice note transcript.
Sort everything into exactly four buckets:
1. ACTIONS, things to be done. Table: task | owner (named human) | due date |
first step. If I did not name an owner, assign to me and flag it.
2. DECISIONS, things I decided out loud. Distinguish carefully between a
decision ("we are moving the launch") and an intention or musing ("we should
probably move the launch"). Put intentions in bucket 4, not here.
3. MESSAGES TO SEND, for every action owned by someone else, draft the
delegation message. Short, includes the why and the deadline.
4. THINKING, ideas, tangents, and half-formed thoughts. Keep them; do not
promote them to actions.
Nothing goes in two buckets. If unsure, put it in THINKING and say why.
<transcript>{paste}</transcript>