Writing good prompts
Write clear prompts using role, context, task, and format building blocks to guide your agent toward better results and more accurate outputs.
Clear prompts give an agent the direction, relevant context, and an idea of what the result should look like. You don't need complicated instructions. A few precise details are often enough.
Here's how to structure prompts, improve results, and standardize recurring tasks.
The four building blocks of a good prompt
A good prompt answers up to four questions. You don't always need all four building blocks. But the more complex the task, the more helpful it is to quickly go through them before sending your prompt.
| Building block | Guiding question | What to include |
|---|---|---|
| Role | Who should respond? | The perspective or expertise you want |
| Context | What does the agent need to know? | Relevant projects, tasks, documents, and background information |
| Task | What specifically should happen? | A clear description of the activity you want |
| Format | What should the result look like? | Length, structure, language, tone, and requested content |
How to write a good prompt
1. Define the role
Describe the role or perspective the agent should respond from. This helps it determine the right tone and area of expertise.
Example: You are an account manager at our agency.
2. Provide the relevant context
An agent needs the right information to handle a task effectively. Use @ to include relevant projects, tasks, and documents. You can also start the agent directly from a task or project so it can take the relevant context into account.
Example: Use the latest updates from @Website Redesign and the notes from our last client meeting.
You don't necessarily have to copy relevant information into the prompt.
3. Describe the task
Be as specific as possible about what you want the agent to do. A clear action verb helps define the task.
Example: Write a status email for the client covering completed work, work in progress, risks, and next steps with dates.
4. Specify the format
Describe what you want the result to look like. If needed, specify the length, language, structure, and tone. You can also say what content to include.
Example: Keep the email under 150 words. Use a friendly tone and write in English.
The prompt defines the role, provides relevant context, describes the task, and gives clear formatting instructions. You can apply this pattern to many other tasks. Simply adjust the role, context, activity, and desired output format.
Best practices for better prompts
Mention content instead of copying it
Use @ to include relevant tasks, projects, and documents. Alternatively, start the agent directly from the relevant area. This lets you use the context that's already available in awork.
For bigger changes, ask for a draft first
Ask the agent to prepare and summarize bigger changes before applying them. That way, you can review the proposed approach before the changes are made.
Improve responses step by step
The first result doesn't have to be perfect. Stay in the same thread and describe exactly what you'd like to change. You don't need to write a completely new prompt.
Examples of short follow-up instructions:
-
Shorter.
-
More formal.
-
Add dates.
Often, one targeted follow-up is enough to improve the existing result.
Reviewing results: What to look out for
Even a convincingly written AI response can contain errors. Check important details before using the result elsewhere.
Pay particular attention to:
-
Numbers: Do they match the source?
-
Dates: Are they correct?
-
Names: Are people's names and other terms spelled correctly?
-
Client-facing text: Review the result before sharing it with a client.
For high-impact tasks, don't treat an AI response as a final result without checking it.
The key points at a glance
A good prompt doesn't have to be long or complicated. What's important is that the task is clear and the agent gets the information it needs.
-
Role: Who should respond?
-
Context: What information should the agent take into account?
-
Task: What should it do?
-
Format: What should the result look like?
Add relevant awork content with @, improve responses step by step, and check important facts before sharing results. If you want to standardize recurring tasks, choose the solution that best fits your workflow.
FAQ
Does every prompt need to include all four building blocks?
No. You don't always need to describe the role, context, task, and format in detail. The more complex the task, the more helpful it is to provide additional information.
Do I need to copy all the context into the prompt?
No. You can mention relevant projects, tasks, and documents with @, or start the agent directly from a task or project.
How do I improve a response that isn't quite right?
Reply in the same thread and describe the change you'd like.
When should I standardize a prompt?
If you enter the same instructions repeatedly, it may be worth saving a prompt. If you need fixed requirements and steps, consider using a Skill. If a task needs its own role, instructions, model, Skills, and connectors, create a custom agent. If you want the task to run without starting it manually, an automated agent is the right option.
Powered by happysupport.ai