Write a useful brief
Describe the result, its constraints and how you will judge it.
Give the assistant decisions it can use
Describe the audience, the main action they should take and the information the result needs. For software, name the pages, important interactions and data. For an agent, name the task, input sources, output destination and actions that require your approval.
Visual requirements are part of the brief. Specify colors, typography, layout, image style and mobile behavior. State whether a reference is inspiration or a layout you want reproduced. Share only material you have the right to use.
Make the request testable
Build a service directory with a search field and filters by city and specialty. Each result opens a detail page. Use navy and cream, a compact header and editorial typography. No payments in this first version. Success means I can filter, open a result and return to the list on mobile.
- List the requirements that must be delivered first.
- Name the existing elements that must be preserved.
- Separate real integrations from sample data or visual demonstrations.
- Use Plan if you want to review the approach before changing files.
For an operational agent
In the connected Notion workspace, read the named project board and summarize overdue tasks in French. Include the source page links and owners. Return the summary here for review. Do not change deadlines or send messages.
Name the account or workspace, the records to use, the output language and where you want the result. Separate preparing a draft from sending or publishing it. The available tools and permissions must support each requested action.
Refine without losing context
After reviewing a result, refer to the specific page, agent or behavior. A request such as ‘keep the colors and navigation; replace only the home-page layout’ gives the assistant a clear boundary. If a real API, payment account or document is missing, resolve that dependency instead of asking it to invent the integration.