Give a clear brief
A useful brief tells Gideon what to produce, what to use, and where to stop. You can give that information in ordinary language.
Include four things
- Outcome: the document, answer, change, or decision you need.
- Context: the files, sources, project, and audience that matter.
- Boundaries: what Gideon may read or change, and what needs your review.
- Done: an observable result, such as a saved file and a list of unresolved questions.
Compare the three proposals attached here for our operations team. Produce a one-page table of scope, delivery dates, and stated costs. Cite each figure to its proposal. Flag missing terms. Do not contact the suppliers. Finish with the questions we need answered.
Ask for a plan when you need one
In an existing chat, open the composer’s + menu and choose Plan this first. Review the draft, edit it, or send feedback. Approve & run it carries the approved plan into work. See conversation controls.
Correct course early
Quote the part you want changed and give a specific correction. For a different approach with the same starting context, branch the chat. For a recurring need, first get one example right; then save a prompt or build a workflow.
Make uncertainty useful
Ask Gideon to distinguish verified facts, assumptions, and missing information. Say what evidence would count as done. For a technical fix, that may be a changed file and a relevant check; for a brief, it may be cited sources and reconciled figures.