> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/resources/prompting-guide.md). # Prompting Guide ## Anatomy of a Prompt {% stepper %} {% step %} ### Role-definition Explain the tool's role for the specific task. For example, "*You are assisting a law firm partner in performing a title deed due diligence*." {% endstep %} {% step %} ### Context Set out the facts surrounding the task that you require the tool to perform. For example, "*The parties have been in dispute for over 20 years, and have now reached a settlement after mediation attempts.*" {% endstep %} {% step %} ### Instructions Direct the exact task that you require the tool to do. For example, "*I need an analysis of the following features of these documents - indemnity, change of control, termination and potential red flags.*" {% hint style="info" %} You can expand and explain each part of the task in detail. Remember, **more specific your instruction, more accurate the response**! {% endhint %} {% endstep %} {% step %} ### Formatting Describe the format - **tables, lists, paragraphs, flowcharts**, etc. You can even specify exact column headings, paragraph lengths, colours for font, shading, etc. This is also an optimal portion to provide templated language or reference. {% endstep %} {% step %} ### Output In the final part, you can mention what the output will be used for. For example, "The output note of arguments will be tendered in court on behalf of the petitioners." {% endstep %} {% endstepper %} {% hint style="info" %} While the tool excels at summarization, analysis, and generating insights, it’s important to * Review outputs carefully for accuracy - particularly for tasks involving voluminous documents. * Understand that legal nuances may require advanced human thinking and judgment. {% endhint %} ## Effective Prompting Techniques

	To Follow	To Avoid	Accessible and Inclusive Considerations
Use the document scope wisely	Select only the documents you need for your task. You are smarter than AI in deciding relevance.	Don’t expect the tool to access external or online sources, or leave out irrelevant sets of documents.	For research, transition to the research tool by selecting relevant text from the responses in Document Review.
Be clear and specific	Use targeted instructions like “Explain the obligations section of this agreement from the buyer's perspective.”	Avoid overly broad prompts like “Summarize this agreement.”	Break complex tasks into smaller, manageable ones for better precision.
Include context	Specify the scope of the task, e.g., “Party ABC has breached the contracted dated 01.02.2000 resulting in severe costs of XYZ. Analyze the indemnity clause in relation to the contract.”	Don’t assume the tool will intuitively focus on the sections you care about without guidance.	Explaining what task you are doing, or what the output is being used for can improve the tool's understanding of your needs.
Guide the format	Specify output preferences, e.g., “Create a table of ....” or “Prepare a comprehensive note with 6 sentences in each paragraph ....”	Avoid ambiguous instructions like “Make it detailed and professional.”	Include desired formats (e.g., `paragraphs`, `bullet points`, text formatting, colours) in your prompts to shape the output.
Rephrase and refine	Iterate and clarify when tackling nuanced issues, by refining your query in the follow-ups for deeper insights.	Don’t assume the AI can provide perfect answers without follow-up prompts.	Tools start with a broad and general approach, but are very receptive to instructions.

## Optimal Usage Tips


Document Scope	The tool reviews only the documents you select - choose wisely, and guide using prompts.
Input Limits	For tasks involving very lengthy documents, focus on specific sections or use multiple prompts for better results.
Output Constraints	If you need to generate lengthy drafts, break it down section-wise into multiple prompts and set specific word limits.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.jurisphere.ai/resources/prompting-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.