Delegate

Speak the ask — hand over a brief, not a guess

What it makes

task brief

General

Real output

A one-line ask, handed off clean

A quick spoken delegation with an owner, a deadline, and one scoping detail.

What you said

Um okay so can you have Priya put together the Q3 social calendar, just the posting schedule not the actual copy, and I need it by end of day Thursday so I can review it before the client call on Friday morning.

What you got

Task

Priya to put together the Q3 social calendar — posting schedule only, no copy.

Owner

Priya

Requirements

A posting schedule covering Q3
Schedule only — no post copy or creative required

Timeline

End of day Thursday (to allow owner review before Friday morning client call)

Done When

Priya has delivered the completed Q3 posting schedule by end of day Thursday and it is ready for review.

Why it’s better

The filler is gone and the one task is crisp — owner, deadline, and the "schedule only, no copy" scope all preserved. It stays a short brief instead of padding out every section, and the one thing you didn't specify — which channels the schedule covers — is surfaced as a question to confirm, not invented into the brief.

A messy ask, made executable

A rambling feature request with several constraints buried in it.

What you said

So when someone deletes a transcript, we show a confirmation modal, that's fine. But after it deletes, there's no feedback and if they deleted wrong one, it's gone. I want like a toast at the bottom that says deleted and has undo for like 5 seconds. If they click undo it restores it. But we also must not mess up if they delete multiple transcripts fast. Also should work in light and dark themes and not be annoying.

What you got

Task

Build a toast notification with an undo action that appears after a transcript is deleted, allowing the user to restore it within 5 seconds.

Owner

Unassigned

Context

Currently, deleting a transcript gives no post-confirmation feedback. If a user deletes the wrong one, there is no recovery path. This adds a safety net without adding friction to the deletion flow.

Requirements

Display a toast at the bottom of the screen immediately after a transcript is deleted
Toast message reads "Deleted" (or equivalent) and includes an Undo button
Undo is available for 5 seconds; after that, the deletion is committed
Clicking Undo restores the transcript to its previous state
Multiple rapid deletions must be handled correctly — each delete gets its own independent undo timer and must not interfere with others
Toast must render correctly in both light and dark themes
Toast must be unobtrusive

Done When

After a transcript is deleted, the toast appears at the bottom of the screen with an active Undo button. Clicking Undo within 5 seconds fully restores the transcript. After 5 seconds without Undo, the transcript is permanently removed. Deleting multiple transcripts in quick succession produces independent, correctly functioning toasts for each. The toast displays correctly in light and dark themes.

Why it’s better

Every constraint you actually said is captured — the 5-second undo, restoring on click, not breaking on rapid deletes, light and dark themes. "Not annoying" stays "unobtrusive" instead of being expanded into specifics you didn't ask for, and no implementation mechanism is invented — the brief tells the developer the WHAT and leaves the HOW to them.

What comes back

A simple one-line delegation comes back as just the task, owner, and "done when" — never padded out with sections that only restate the ask.
A messy multi-requirement ask comes back fully structured: every constraint you said is captured, nothing you didn't is added.
Delegate several distinct things in one breath and you get one clean brief per task, ordered by priority.
It briefs the WHAT, not the HOW — it won't lock in a tool, mechanism, or design you left open; that becomes an open decision instead.

What you can count on

Never invents specifics — a vague "make it premium" stays at your altitude, with the gaps surfaced as questions, not a fabricated spec
Keeps what you said and only what you said — background you mention ("we already use X") stays context, not a requirement you never asked for
Scales honestly — one-line asks stay short, real projects get the full structure, and nothing is padded

Install Delegate and try it on your own voice.

Is this hat for you?

Shape rough spoken thoughts into a clear, runnable delegation brief.

Delegate turns a rambled, half-organized ask — "can you have someone do X, oh and it needs Y, by Thursday" — into a clean brief the person you hand it to can actually run with: the task, who owns it, what "done" means, and any dependencies or deadline, scaled to how big the ask really is. Its discipline is what makes it trustworthy. It briefs what you actually said and never pads or invents. Vague spots don't get filled with made-up specifics — they're surfaced as a short list of assumptions you can correct, so "make it feel premium" stays "make it feel premium" instead of turning into a fake spec. A one-line task comes back as a few lines; a real project comes back fully structured. You talk; your teammate, contractor, or future self gets something executable.

Best for

Handing a task to a teammate, contractor, or freelancer — talk it through, get a brief they can act on without a follow-up call
Turning a rambling "we should do X, and also Y, and don't forget Z" into one clean brief per task, priority-ordered
Capturing a delegation on the move — between meetings, walking to your car — into something structured you can send
Briefing your future self: a task you'll pick up later, with the context and "done" criteria intact

Not for

A quick message or reply to send as-is — Delegate writes a task brief, not a message (reach for Clarity or Work Email)
Pulling decisions and notes out of a meeting (reach for Meeting Notes or Distill)
A polished spec you'll publish — Delegate briefs what you said and flags the gaps; it won't design the missing details for you

Using it

How it works

Just talk through the task — who should do it, what it is, why it matters, when it's due. Ramble; Delegate organizes it.
It pulls out the real task, assigns the owner you named (or marks it "Unassigned"), and defines what "done" looks like.
It scales to the ask: a one-liner stays a few lines; a multi-part project gets requirements, dependencies, and a timeline.
Where you were vague, it picks a sensible default and surfaces it as an assumption you can confirm or correct — it never quietly invents the specifics.

Try saying

can you have Marcus refresh the pricing page copy by Friday, the headline's out of date and the plan names changed
I need someone to put together the Q3 social calendar, just the posting schedule not the copy, by end of day Thursday
okay so two things for the team — first fix the login bug that's highest priority, and then whenever there's time start scoping the export feature

Tips

Name the owner if you have one — "have Priya do X" — and Delegate assigns it; if you don't, it marks the task Unassigned.
Say the deadline out loud if there is one; Delegate includes it, and never invents one if there isn't.
It's fine to be vague — "make it better" is okay. Delegate won't guess the specifics; it'll flag them as questions for you to answer.