Prompt Almanac

Create beginner Works with: Any AI

Asana Task Description From a Rough Request

Structured brief Has example

Write clear task text that the assignee can act on.

Open in ChatGPTOpen in Claude

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Rate this prompt

Loading ratings…

Rewrite this rough request as an Asana task. Request: [ROUGH_REQUEST]. Requester: [REQUESTER]. Due date and reason: [DUE_AND_REASON]. Files or links that exist: [LINKS]. My projects and sections: [PROJECTS_AND_SECTIONS]. Glossary: [GLOSSARY].

Produce a task name that starts with a verb and says what finished looks like (under 70 characters), then a description with Goal, Context, What done looks like (as a checklist), Inputs and links, and Who to ask. Write in plain text that survives pasting into Asana's editor, using simple dashes for lists, and keep it under 150 words with the checklist as the main body. Suggest the project and section from my list, and subtasks only when the work has distinct steps with different owners or dates.

Make it usable by someone who was not in the conversation: replace pronouns such as it or that with what they refer to and expand abbreviations not in my glossary. If the request is ambiguous, list the two questions the assignee would otherwise have to ask, phrased so the requester can answer in one line. Never invent a deadline, owner or budget. If the work is bigger than about two days for one person, say so and suggest splitting it.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

See an example result (fictional data)
Rough request: 'Can someone sort out the customer survey results soon?'
Task name: Summarise Q1 customer survey results for the leadership meeting. Goal: one-page summary with the top three findings. Context: survey closed on 15 March with 212 responses. Done when: the summary is reviewed by the head of service and uploaded to the shared folder. Inputs: survey export link. Due: 28 March (requested by the head of service for the 2 April meeting). Who to ask: head of service. Subtasks: clean the export, calculate scores by question, draft findings, review. Questions for the requester: which questions matter most, and should free-text comments be included?

Illustrative only, made-up data. Your results will differ and must be reviewed.

Related prompts