Write Effective Task Briefs
Use goals, context, materials, and acceptance criteria to get usable results from Nexts faster.
What a good task includes
- Goal: what you ultimately want to end up with.
- Context: why it matters, who it's for, and any constraints.
- Materials: the files, web pages, emails, or meeting content to read.
- Deliverable: a document, spreadsheet, code change, checklist, or recommendation.
- Acceptance criteria: what counts as done, and what must not change.
Example
Instead of just saying:
Help me tidy up this project.
Try:
Read the requirements and meeting notes in the project folder and put together an execution plan for this week. List tasks by priority with owners, dependencies, and risks. Don't modify the original files — show me a preview in the conversation first.
Adjusting mid-task
If the result is heading the wrong way, say directly what to keep and what to change. For example: "Keep the current structure, make the tone more concise, and sort the risks from highest to lowest impact."
For high-risk or bulk operations, ask Nexts for a plan and a preview first, then approve execution.