Legal Prompting Cheat Sheet
Use this Cheat Sheet to master legal prompting with AI
Power Prompt (Tab)
Start typing your request, then press Tab. Power Prompt instantly expands and refines your wording with AI, so your query is clearer before you hit Enter.
Roles
- Summariser – Condense email threads, meeting transcripts, or lengthy documents into key points.
- Drafting Assistant – Generate first-pass text for documents, emails, or presentation speaker notes.
- Spreadsheet Analyst – Interpret data, spot trends, and suggest charts in spreadsheets.
- Meeting-Note Generator – Turn calendar events + meeting details into structured minutes and action items.
- Policy Checker – Review documents or presentations for compliance with internal guidelines.
- Negotiator – Propose redlines and concession-based talking points within contract documents.
- Devil’s Advocate – Stress-test an argument or proposal by exposing weaknesses.
Output Formats
- Plain text / Prose
- Bulleted list
- Numbered checklist
- Markdown table (quick comparisons)
- Email draft
- Document outline
Writing Tones
- Formal & Professional
- Objective & Neutral
- Concise & Direct
- Persuasive & Advocating
- Explanatory & Clear
- Firm & Assertive
Example
-
You type:
Draft a summary of yesterday’s Q2 budget review
-
You press Tab (Power Prompt expands to):
Act as Summariser. Summarise key decisions, action items, and budget changes from yesterday’s Q2 budget-review meeting (see attached Meet transcript). Return a bulleted list suitable for a follow-up email in a formal, concise tone.
-
Assistant returns:
A crisp, bullet-point summary ready to paste into an email.
Instantly Navigate Long Email Threads
Summarize & Action Email Threads
Forward your long email threads to assistant@wordsmith.ai.
Then, use the prompt below with the AI assistant to get a clear timeline of interactions and a list of key actions required.
Email Thread Timeline & Action Extractor
Analyzes an email thread to create a chronological timeline of interactions and identify outstanding actions, tailored for UK legal/business context.
Goal:
The goal is to analyze a provided email thread or communication log to create a detailed timeline of interactions with another party. This timeline will serve to clarify the sequence of discussions, agreements, and pending actions, enabling a clear understanding of the current status and required steps.
Instructions:
1. Input Analysis:
* Carefully examine the provided email thread or communication log, paying close attention to dates, times, senders, recipients, and the content of each message.
2. Timeline Creation:
* Extract each distinct interaction (e.g., email sent, email received, meeting, phone call) and arrange them chronologically.
* For each interaction, identify:
* Date and time of the interaction.
* Participants involved (sender and recipient).
* A concise summary of the main topics discussed or agreed upon.
* Any specific actions agreed upon or requested from either party.
3. Action Identification:
* Based on the timeline, identify all outstanding actions required from your side (the user).
* For each action, specify:
* A clear description of the action.
* The reason the action is necessary (reference the relevant interaction in the timeline).
* The suggested deadline or timeframe for completion (if applicable).
4. Explanatory Writing Style:
* Present the information in a clear, concise, and easily understandable manner. Avoid jargon and explain any technical or legal terms if they are present in the email thread.
5. Jurisdiction:
* The analysis should be performed within the context of the legal and business practices relevant to the United Kingdom.
Answer Format:
Use markdown to format your response for clarity and readability.
# Timeline of Interactions
| Date/Time | Participants | Topic(s) Discussed | Actions Agreed Upon |
|---|---|---|---|
| \[Date and Time of Interaction 1] | \[Sender(s) and Recipient(s)] | \[Brief Summary of Topics] | \[Agreed Actions (if any)] |
| \[Date and Time of Interaction 2] | \[Sender(s) and Recipient(s)] | \[Brief Summary of Topics] | \[Agreed Actions (if any)] |
| \[Date and Time of Interaction 3] | \[Sender(s) and Recipient(s)] | \[Brief Summary of Topics] | \[Agreed Actions (if any)] |
| ... | ... | ... | ... |
# Key Actions Required
| Action | Reason (Reference Timeline) | Deadline/Timeframe |
|---|---|---|
| \[Description of Action 1] | \[Reference specific interaction(s) in the timeline] | \[Suggested Deadline] |
| \[Description of Action 2] | \[Reference specific interaction(s) in the timeline] | \[Suggested Deadline] |
| \[Description of Action 3] | \[Reference specific interaction(s) in the timeline] | \[Suggested Deadline] |
| ... | ... | ... |
Multi-Agent Workflow Guide
Core Tool Chains
Wordsmith's multi-agent system excels at chaining these core tools. Combine them in a single prompt to automate complex tasks.
🔄 Document Conversion: Transform formats (PDF ↔ Word).
🌐 Web Analysis: Analyze web pages, check links.
🔗 Web Page Reader: Extract content from a URL.
🌍 Translation: Convert documents (40+ languages).
⚖️ Comparison: Identify version differences. (Works best for two versions of the same contract)
✍️ Drafting: Create new documents.
📋 Review: Automated analysis via playbooks.
Powerful Workflow Combinations
- Document Processing & Translation: "Convert this PDF contract to Word, then translate it to French."
- Web Research to Document: "Analyze these 3 company websites (use Web Page Reader for each), check for privacy policy links, then draft a comparative privacy assessment."
- Multi-Document Analysis & Drafting: "Compare these 2 versions of the DPA, identify key changes, then draft a summary of amendments."
- Complete Document Lifecycle (Simplified): "Take this draft employment agreement, review it for completeness using your standard playbook, then provide a clean PDF for signing."
Specialized Review Playbooks
Trigger expert analysis by telling the agent what kind of document it's looking at:
"Review this as an NDA"→ Automated confidentiality analysis."Review this as a DPA"→ GDPR compliance checking."Review this as a SaaS vendor agreement"→ Service level and commercial terms analysis.
Helpful Starter Prompts to Try
-
Research-to-Contract Pipeline
Analyze competitor privacy policies, draft a new one incorporating best practices, review for GDPR, and export as PDF.
Analyze the privacy policies on the following websites: [URL A], [URL B], and [URL C]. Based on your analysis, draft a new comprehensive privacy policy for our company, 'Innovate Inc.', that incorporates the best practices you identified regarding data collection, user rights, and cookie usage. After drafting, review the new policy for compliance with GDPR principles. Finally, export the completed and reviewed policy as a PDF document. -
Analysis-to-Communication Chain
Review an MSA's liability/data clauses, then draft an email summarizing risks and negotiation points.
Review the attached Master Services Agreement. Pay special attention to the 'Limitation of Liability', 'Indemnification', and 'Data Processing' clauses. After completing your review, draft an email to our General Counsel, Jane Doe. The email should concisely summarize the top 3 highest-risk items you identified and propose a specific, actionable negotiation point for each risk. -
Agreement Deliverables Tracking Table
Generate a comprehensive table of key deliverables (legal, regulatory, operational, financial) from an agreement, including responsibilities, due dates, and dependencies.
## Goal: You are a legal expert tasked with creating a comprehensive table of key deliverables for the Company following the execution of a significant agreement. The goal is to ensure that all legal, regulatory, operational and financial obligations are clearly outlined, including execution of ancillary documents, regulatory filings, notices, internal approvals, financial obligations, and post-closing covenants. This table will serve as a critical tool for stakeholders to track and fulfill their responsibilities, ensuring compliance with the agreement and minimizing potential risks. ## Instructions: To create this comprehensive table, review the agreement thoroughly to identify all obligations and requirements. Consider the following key areas: - **Legal Obligations**: Execution of ancillary documents, regulatory filings, and compliance with laws and regulations. This includes reviewing all clauses related to legal requirements, such as contract signing, notarization, and registration where applicable. - **Regulatory Obligations**: Filings, notices, and submissions required by regulatory bodies. Identify all regulatory requirements, including deadlines for submissions and the responsible parties for each. - **Operational Obligations**: Internal approvals, notices to stakeholders, and implementation of operational changes. This encompasses changes in business practices, IT systems, or any other operational aspect that needs adjustment following the agreement. - **Financial Obligations**: Payments, security interests, and other financial commitments. Detail all financial responsibilities, including payment schedules, interest rates, and any collateral required. When structuring the table, ensure that it includes all necessary details for each deliverable, focusing on clarity and conciseness. Each entry should be straightforward, allowing stakeholders to quickly understand their tasks and deadlines. ## Answer Format: The table will be structured with the following columns: - **Deliverable Name**: A concise name for each deliverable. - **Clause Number**: The specific clause in the agreement that pertains to the deliverable. - **Description**: A clear explanation of the deliverable, including any specific actions or outcomes required. - **Responsible Party**: The individual, team, or department responsible for ensuring the deliverable is completed. - **Due Date**: The deadline by which the deliverable must be completed. - **Dependencies**: Any preconditions or related tasks that must be completed before the deliverable can be finished. - **Approval/Submission Requirement**: Details on whether the deliverable requires approval from a specific party or submission to a regulatory body, and if so, the process for obtaining such approval or making the submission. Always include citations. Example of a table entry: | Deliverable | Clause Number | Description | Responsible Party | Due Date | Dependencies | Approval/Submission Requirement | | --- | --- | --- | --- | --- | --- | --- | | Execution of Ancillary Documents | 3.1 | Signing and notarization of all ancillary documents. | Legal Team | 14 days post-agreement | Review of agreement terms | Submission to Regulatory Body A | ### Key Obligations and Requirements Highlight any critical obligations or requirements that are not explicitly listed as deliverables but are essential for compliance with the agreement. This could include ongoing monitoring requirements, periodic reporting, or maintenance of specific standards. ### Regulatory and Compliance Considerations Outline any regulatory or compliance considerations that must be addressed in conjunction with the deliverables. Discuss how these considerations impact the implementation of the agreement and any additional steps that must be taken to ensure full compliance. Format your answer using markdown to ensure clarity and readability. The table should be comprehensive, covering all aspects of the agreement, and easy to follow for stakeholders responsible for implementing the obligations outlined in the agreement. -
Legal Opinion Review & Critique
Review a legal opinion, flagging issues, assumptions, and areas for clarification using a structured markdown output.
# Goal Review the attached legal opinion and highlight potential issues, assumptions, and areas needing clarification. --- # Instructions 1. Flag: - Unsupported assumptions - One-sided conclusions - Outdated references - Conflicts with known jurisdictional guidance 2. Use citations where possible to support comments. 3. Be neutral and constructive in tone. --- # Output Use markdown to structure your feedback by section: - ## Summary - ## Key Issues - ## Assumptions / Gaps - ## Action Items Use ❗, ⚠️, and ✅ to visually tag criticality of each issue.