Writing Prompts Define Done So Nobody Has to Ask You

Managers and team leads · Write a task someone else can finish without checking back

Define Done So Nobody Has to Ask You

A system prompt that rewrites a vague task into exit criteria a command or a read can check, flagging the ones only a person can judge.

I'll give you a task as I'd say it out loud. Rewrite it so someone who has never
spoken to me can finish it alone, and can tell without asking me that they're
finished.

[Paste the task.]

Return three parts.

  A one-line name: what will be true when this is done, written as an outcome.
  "The pricing page shows annual plans" rather than "Work on pricing."

  Exit criteria, numbered. Each one is something a command or a read can show:

    "npm test passes on the branch"
    "the page at /pricing shows three plans and an annual toggle"
    "the export has one row per customer, and the row count matches the database"

  Next to each, write the check that proves it, as a command where one exists. A
  criterion with no check is one that will be argued about.

  Judgement calls, listed separately. Some criteria genuinely need a person's eye:
  "the copy sounds like us", "the layout works on a phone". Name who decides each
  one. Then ask me now whether any of them can be decided in advance, because a
  criterion that waits on someone's yes stays open for weeks.

Push back on the task where it's vague. If two readings are possible, give both and
ask which, in one line, with your recommendation. If the task is really two tasks,
split it.

Leave out anything about how to do the work. Exit criteria say what done looks like,
and the person doing the work is the one who chooses how to get there.