Starting a new AI conversation can feel like joining a meeting where nobody has read the previous notes. You explain the goal, repeat the constraints, and discover that an old decision has become a suggestion again. A compact context brief gives the next conversation a more reliable starting point.
The brief is a document you control. It captures what a collaborator needs to understand the work today. Set aside 20 minutes to create one for a single project, using whichever writing tool you prefer.
1. State the objective: three minutes
Describe the result you are working towards and who it serves. “Help with my business” is too broad to guide a useful response. “Draft a clear service page for independent design clients” gives the conversation a purpose.
Include the current stage. Researching an idea, choosing a direction, and polishing a draft call for different help. If success is still uncertain, say what you are trying to learn.
2. Capture the context that changes the answer: six minutes
Add the current state, important decisions, constraints, and open questions. Keep each section short. A useful test is: would leaving out this detail make the next answer meaningfully worse?
- Current state: what exists, what has been checked, and what remains uncertain.
- Decisions: the choices you have made and the reasons worth preserving.
- Constraints: boundaries such as time, scope, voice, or information you cannot claim.
- Sources: the files or excerpts that support factual statements.
- Open questions: what you have not decided yet.
Separate facts from assumptions. “Three interviewees mentioned onboarding confusion” and “onboarding is the main problem” are different statements. The first describes evidence; the second needs interpretation. The decision journal guide offers a simple way to preserve that distinction.
3. Use this copyable structure: five minutes
Project and date: ___
Objective and audience: ___
Current stage: ___
Known facts and source locations: ___
Decisions already made, with reasons: ___
Constraints and things to avoid: ___
Open questions or assumptions: ___
What I need from this conversation: ___
Output format: ___
Finish with an explicit request. A context brief explains the situation; a request tells the AI what to do with it. Ask for a draft, a comparison, a set of questions, or a critique, then define what you want back.
A worked example: a consultant’s service page
Project and date: design research service page, 21 October.
Objective: help small product teams decide whether to enquire.
Current stage: outline ready; first draft needed.
Known facts: the service includes interviews and a findings workshop; details are in the attached service outline.
Decisions: focus on one service so the page is easy to understand.
Constraints: warm, direct voice; no invented testimonials or outcome promises.
Open question: whether pricing belongs on this first version.
Request: draft the page and flag any factual gaps.
Format: headline, introduction, process, fit, and enquiry invitation.
The example contains enough direction to begin while leaving the pricing question open. It gives the AI permission to identify gaps instead of filling them with confident guesses.
4. Check and maintain it: six minutes
Read the brief as though you had never seen the project. Remove outdated instructions and sensitive information the next task does not require. Add dates to facts that may change. If you mention a file, confirm that the tool or person receiving the brief can actually access it.
At the end of a useful conversation, update only what changed: a decision, a new fact, a next action. Review the brief when the project changes direction. This is easier when your notes have a deliberate home; the second brain guide explains that wider practice.
Does a brief guarantee continuity?
No. Tools differ in what they can access and retain, and they can still misread instructions. Check important outputs against your sources. A brief improves the information you provide; it does not replace your judgement.
Continuity across AI sessions is part of the intended direction for Socratis OS. Read how Socratis OS is being developed, or join the early-access waitlist.



