Turn a Slack or Email Request into a Clear Task Brief with a Deadline

Paste a messy Slack message or email and get a task brief with owner, deliverable, due date, a done checklist, and a ready-to-send reply asking for missing details.

You getTask title, requester / Owner / Stakeholders and deliverable

Prompt

Prompt
You are an experienced project coordinator who turns vague requests into clear, actionable task briefs.

I will paste a Slack message, email or thread right after this prompt. Turn it into a task brief I can act on or forward.

Rules:
1. Use only what the request says. If the owner, deadline or scope is not stated, write "Not stated" and add it to the questions. Never guess a date.
2. Convert relative dates ("end of week", "before the offsite") into a specific day and date only if the message gives enough context. Otherwise flag it as unclear.
3. Write the deliverable as one sentence that starts with a verb and names the format (doc, deck, spreadsheet, code change).
4. Write 3-5 done criteria that someone else could check with a yes or no.
5. List at most 5 questions, each answerable in one line, ordered by how much they block the work.

Output format:
- Task title (under 10 words)
- Requester / Owner / Stakeholders
- Deliverable
- Due date (marked as stated, inferred or missing)
- Context (2-3 bullets)
- Definition of done (numbered checklist)
- Open questions (numbered)
- Reply message under 80 words that asks those questions, ready to send

End with one line naming the biggest risk to hitting the deadline as written.

Example output

At a glanceTask brief built from a vague Slack requestExample: Dana Whitlock asks for a Q2 churn summary before the leadership offsite
  1. Task titleQ2 Customer Churn Summary for Leadership Offsite
  2. PeopleRequester Dana, owner you, Marco on billing data
  3. Due dateMissingOnly "before the leadership offsite", no date given
  4. Definition of done5 checks, e.g. top 3 churn reasons with counts
  5. Open questions5 questions on date, format, scope and Marco
  6. Reply messageReady-to-send note to Dana asking the 5 checks

Example for: a Slack message sent Tuesday, 10 June, from Dana Whitlock (Head of Customer Success) to an analyst: "hey can you pull together something on why we lost customers last quarter? need it before the leadership offsite, nothing fancy, maybe loop in Marco for the billing side. thx!"

Task title

Q2 Customer Churn Summary for Leadership Offsite

Requester / Owner / Stakeholders
  • Requester: Dana Whitlock, Head of Customer Success
  • Owner: You (the recipient). Not explicitly assigned, but implied
  • Stakeholders: Marco (billing data), leadership offsite attendees
Deliverable

Prepare a short summary (format not stated: doc or slides) explaining the main reasons customers churned in Q2.

Due date

Missing. "Before the leadership offsite" is the only reference, and no offsite date is given.

Context
  • Audience is leadership, so the summary should lead with the top reasons, not raw data.
  • "Nothing fancy" suggests a light format, not a polished deck.
  • Billing data from Marco is expected to be part of the analysis.
Definition of done
  1. The summary names the top 3 churn reasons, each backed by a count or percentage of churned accounts.
  2. It states the total number of accounts lost in Q2 and the data source used.
  3. Marco has reviewed the billing-related findings.
  4. It is delivered in the format Dana confirmed, at least one working day before the offsite.
  5. It fits on one page or no more than 3 slides.
Open questions
  1. What is the offsite date, and when do you need this in hand?
  2. Doc or a few slides?
  3. Does "last quarter" mean Q2 (April–June)? If so, June isn't over yet. Should I cut off at a specific date?
  4. Should I include downgrades, or only full cancellations?
  5. Has Marco been told he's involved?
Reply message

Hi Dana, happy to take this on. A few quick checks so I get it right:

  1. When's the offsite, and when do you need this?
  2. Doc or a few slides?
  3. Q2 is still in progress. OK to cut off at 31 May?
  4. Full cancellations only, or downgrades too?
  5. Have you looped in Marco, or should I?

Biggest risk: With no offsite date and an unfinished quarter, the deadline and data window could both shift late.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Forcing "Not stated" instead of guesses stops the model from inventing deadlines or owners that you'd then act on.
  • Yes/no done criteria make the scope checkable, so you and the requester agree on what finished looks like.
  • The ready-to-send reply turns gaps into one quick message instead of a back-and-forth thread.

Use this when a request lands in Slack or your inbox and you're not sure what's actually being asked. Copy the full message or thread, paste it after the prompt in ChatGPT, Claude or Gemini, and include the date it was sent.

Common edits

  • Add your team's task tool fields (priority, project, labels) so the brief pastes straight into Asana, Jira or Trello.
  • Ask for a shorter reply in a casual Slack tone, or a more formal one for email to a client.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Productivity