Grok Bot legal prompts that stop before anyone files
Standing jobs for a teammate with a browser, files, and a terminal. The Bot tracks dockets and drafts packs. You or a human lawyer review, sign, and file. Not legal advice, and not grok.com chat.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Deadlines and intake
5 promptsPull the docket for one matter
1/21✨ What it does
The Bot opens [COURT PORTAL] for [MATTER], copies hearings and filing dates into a dated table, and flags anything due in [N] days. You check the dates against the file and you calendar what you will meet.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a dated docket table for [MATTER] from [COURT PORTAL]. Flag anything due in [N] days. Do not file. Sources: [COURT PORTAL] in the cloud browser, [CASE NUMBER], [MATTER FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - This is not legal advice. Do not file. Do not email the clerk as me. - If the portal needs a login, 2FA, or a CAPTCHA, hand me the computer. Do not invent a hearing date. Deliverable: Table: date, event, source URL or stamp, due-in-N (yes/no), unknown if the portal is down. Review point: I calendar. I file.
Pro tip: Name the portal and the case number. "The court site" is how the Bot logs into the wrong county.
Response-deadline card from the rules
2/21✨ What it does
The Bot reads [RULE SET] and [TRIGGER DATE] and builds a response-deadline card with the math, the source paragraph, and any weekend or holiday catch. You confirm the date with counsel before anyone files.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compute the response deadline from [RULE SET] and [TRIGGER DATE]. Show the math and the paragraph you used. Sources: [RULE SET] file or URL, [HOLIDAY CALENDAR], [TRIGGER DOC]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - This is not legal advice. Do not file. Do not tell a client this date is final. - If the rule is silent on weekends or service method, write unknown. Do not pick a date to be helpful. Deliverable: Trigger, rule cite, computation, weekend/holiday note, confidence, open questions for counsel. Review point: Counsel confirms. I file.
Pro tip: Write the trigger event, not "when we got served." A wrong start date is how defaults happen.
Intake memo from the first email pile
3/21✨ What it does
The Bot turns [INTAKE INBOX] for [DATE RANGE] into one memo per new matter: parties, ask, dates, attachments, and missing facts. You decide which matters open and you sign any engagement.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write one intake memo per new thread in [INTAKE INBOX] for [DATE RANGE]. Do not open a matter. Sources: [INTAKE INBOX] via the cloud browser, attachments saved to [FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send an engagement letter. Do not e-sign. Do not email the sender as me. - If a name is unclear, write unknown. Do not invent a party or a date. Deliverable: Per thread: parties, ask, dates, files, missing facts, draft next question for me. Review point: I open the matter. I sign the engagement.
Pro tip: One memo per thread. A pile of forwards is not one client.
Conflict check against the roster
4/21✨ What it does
The Bot compares names in [NEW MATTER NOTES] to [CLIENT ROSTER] and [ADVERSE LIST] and returns hits, near-hits, and unknowns with the source row. You run the real conflict check and you decide if the firm can take the work.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare names in [NEW MATTER NOTES] to [CLIENT ROSTER] and [ADVERSE LIST]. Return hits, near-hits, and unknowns. Sources: [NEW MATTER NOTES], [CLIENT ROSTER], [ADVERSE LIST], [PRIOR MATTER INDEX] if you have one. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email the prospective client. Do not open a matter. Do not e-sign a waiver. - This is a first pass, not the firm conflict system. If a roster file is missing, stop and say so. Deliverable: Name, match type (hit / near / unknown), source row, other entities on the same thread. Review point: I run the official conflict check. I take or decline the work.
Pro tip: Near-hits matter. Acme Inc and Acme Holdings are not a pass.
Filing-receipt dump from the e-file inbox
5/21✨ What it does
The Bot saves stamped receipts and notices from [E-FILE INBOX] for [MATTER] into [FOLDER], named by date and document type. You confirm each stamp against the docket and you file nothing from this job.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Save stamped receipts and court notices for [MATTER] from [E-FILE INBOX] into [FOLDER]. Do not file anything new. Sources: [E-FILE INBOX] in the cloud browser, [MATTER FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not file. Do not reply to the court mailbox. Do not send anything to opposing counsel. - If a full social-security number or account number appears, stop and tell me. Do not forward the mail. Deliverable: File list with paths, missing stamps vs the last docket, anything that looks like a new deadline. Review point: I confirm the stamps. I file only from the official tool.
Pro tip: Keep the stamp in the filename. A renamed PDF is how you lose proof of filing.
Contract drafts
4 promptsRedline against the playbook
6/21✨ What it does
The Bot redlines [CONTRACT] against [PLAYBOOK], quotes each flagged clause, and proposes insert language marked as a draft. You or a human lawyer pick the redlines and you do not e-sign from the Bot.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Redline [CONTRACT] against [PLAYBOOK]. Quote each flag. Mark every insert as a draft. Do not send it. Sources: [CONTRACT] file, [PLAYBOOK], [PRIOR MARKUP] if I attach one. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send the redline to opposing counsel. Do not e-sign. Do not file this draft. - This is not legal advice. If a clause is missing from both docs, say missing. Do not write a fake house position. Deliverable: Table: clause, quote, playbook cite or silent, draft insert, risk note. Review point: Counsel picks the redlines. I send. I sign.
Pro tip: If the playbook is silent, write silent. Do not invent firm policy to close a gap.
Three-strength clause insert
7/21✨ What it does
The Bot drafts a [CLAUSE TYPE] for [ROLE] under [GOVERNING LAW] in standard, aggressive, and fallback versions, with a note on each term. You choose the version and a lawyer signs the paper.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a [CLAUSE TYPE] for [ROLE] under [GOVERNING LAW] in standard, aggressive, and fallback form. Sources: [PLAYBOOK], [FIRM CLAUSE FILE], [DEAL NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not insert the clause into a live contract and send it. Do not e-sign. Do not send it to opposing counsel. - This is not legal advice. Flag if [GOVERNING LAW] is missing or if enforceability is unknown. Deliverable: Three versions, term notes, likely pushback, questions for counsel. Review point: I choose the version. Counsel signs.
Pro tip: Put governing law in the brief. A clause with no jurisdiction is fanfic.
Engagement letter the client still signs
8/21✨ What it does
The Bot drafts an engagement letter for [MATTER] with scope, exclusions, [FEE STRUCTURE], and a signature block, using [FIRM TEMPLATE] if you have one. You edit the scope and the client or a partner signs.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft an engagement letter for [MATTER] from [FIRM TEMPLATE]. Scope and exclusions must be specific. Do not send. Sources: [FIRM TEMPLATE], [INTAKE MEMO], [FEE STRUCTURE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send this to the client. Do not e-sign for a partner. Do not file it as a court paper. - This is not legal advice and not a substitute for your ethics rules. If the template is missing a required block, say missing. Deliverable: Draft letter path, exclusions list, open questions, signature block left unsigned. Review point: I edit. A partner or I send. The client signs.
Pro tip: Exclusions are the job. Vague scope is how you work for free and still get a complaint.
Version compare of two drafts
9/21✨ What it does
The Bot diffs [DRAFT A] against [DRAFT B] on defined terms, money, term, exit, liability, and IP, and lists what moved with quotes. You pick the version that goes out and you do not send it to the other side.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Diff [DRAFT A] vs [DRAFT B] on defined terms, money, term, exit, liability, and IP. Quote what moved. Sources: The two files I point at in [FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send either draft to opposing counsel. Do not e-sign. Do not file a version. - If a section exists in only one draft, say so. Do not blend the two into a third "helpful" contract. Deliverable: Section table with quotes, money deltas, unsigned items, open questions. Review point: I pick the version. I send it.
Pro tip: Quote both sides. A paraphrase of a liability cap is how you miss a zero.
Discovery pack
4 promptsPrivilege log from the review set
10/21✨ What it does
The Bot builds a privilege-log draft from [REVIEW SET] with date, authors, privilege claimed, and a one-line description, marking thin rows as unknown. You privilege-review every row before anyone logs or produces it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a privilege log from [REVIEW SET]. Unknown if authors or a basis are missing. Do not produce. Sources: [REVIEW SET] on the computer, [LOG TEMPLATE], [CUSTODIAN LIST]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not produce this log. Do not send it to opposing counsel. Do not file it. - This is not legal advice. Do not invent a privilege basis. Privilege calls stay with me or counsel. Deliverable: Draft log, unknown rows, docs that look like they should be on the log but are not, path. Review point: I privilege-review. Counsel signs the log.
Pro tip: If you cannot see the authors, the row is unknown. Do not guess privilege.
Production index with Bates gaps
11/21✨ What it does
The Bot indexes [EXPORT] into a Bates map with range, custodian, date span, and gaps, plus a missing-page list. You approve the index before anyone produces a document.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Index [EXPORT] into a Bates map: range, custodian, date span, gaps. Do not produce and do not renumber. Sources: [EXPORT] folder, [BATES MANIFEST] if any, [CUSTODIAN LIST]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not produce documents. Do not send the index to opposing counsel. Do not file the index. - If a range is unreadable, write unknown. Do not invent Bates numbers. Deliverable: Range table, gap list, custodian coverage, path to the index file. Review point: I approve. I produce from the official tool.
Pro tip: Gaps stay visible. Do not renumber to make the index pretty.
Litigation-hold draft for custodians
12/21✨ What it does
The Bot drafts a litigation-hold notice for [CUSTODIANS] on [MATTER] from [HOLD TEMPLATE], naming systems to keep and what not to delete. You review the draft and you send the hold.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a hold notice for [CUSTODIANS] on [MATTER] from [HOLD TEMPLATE]. Name systems. Do not send. Sources: [HOLD TEMPLATE], [SYSTEM LIST], [MATTER NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send the hold. Do not email custodians. Do not send anything to opposing counsel. - Do not delete or alter files "to tidy the hold." If a system is unknown, write unknown. Deliverable: Draft notice, custodian list, systems named, missing-system questions. Review point: Counsel reviews. I send the hold.
Pro tip: Name systems. "Preserve relevant data" is not a hold.
Interrogatory answer pack from the facts folder
13/21✨ What it does
The Bot drafts answers to [ROGS OR RFPS] from [FACTS FOLDER], cites the file for each answer, and writes unknown when the folder is silent. You and counsel verify every cite before anyone serves a response.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft answers to [ROGS OR RFPS] using only [FACTS FOLDER]. Unknown if the folder is silent. Do not serve. Sources: [ROGS OR RFPS], [FACTS FOLDER], [PRIOR ANSWERS] if I point at them. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not serve answers. Do not send them to opposing counsel. Do not file a response. - This is not legal advice. Do not invent a fact, a date, or a cite. Privilege calls stay with counsel. Deliverable: Per request: draft answer, file cite or unknown, privilege flag, questions for me. Review point: Counsel verifies. I serve.
Pro tip: Cite the folder or write unknown. Invented facts in an answer are a sanction.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Matter hygiene
4 promptsMatter folder hygiene
14/21✨ What it does
The Bot audits [MATTER FOLDER] for misnamed files, duplicates, missing stamps, and drafts sitting next to produced sets, and proposes a rename list. You approve every move before a file is renamed.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Audit [MATTER FOLDER]. Propose renames and a split between working drafts and produced sets. Do not delete. Sources: [MATTER FOLDER] on the computer, [PRODUCTION MANIFEST] if any. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not delete produced files. Do not file anything. Do not email the folder to opposing counsel. - Do not overwrite a stamped PDF. If two files look the same, list both. Deliverable: Rename list, duplicate pairs, missing stamps, proposed folder split, nothing applied. Review point: I approve moves. I do not let it delete the working set.
Pro tip: Produced sets are frozen. Propose moves. Do not tidy them.
Time narratives from the calendar
15/21✨ What it does
The Bot turns [CALENDAR] plus [NOTES] for [WEEK] into draft time entries with matter, narrative, and hours, and flags anything that looks like a privileged client call. You edit the narratives and you post the time.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft time entries for [WEEK] from [CALENDAR] and [NOTES]. Flag privileged-looking calls. Do not post time. Sources: [CALENDAR], [NOTES], [MATTER CODES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not post time. Do not email a prebill. Do not send narratives to opposing counsel. - Do not quote a client verbatim in a narrative. If the matter code is missing, write unknown. Deliverable: Draft entries: matter, hours, narrative, privilege flag, source event. Review point: I edit. I post time.
Pro tip: Privileged call notes stay vague in the narrative. You edit before posting.
Redact before a pack leaves the firm
16/21✨ What it does
The Bot redacts emails, phones, national IDs, and account numbers from [PACK], lists the types it removed, and keeps matter IDs. You review the redacted copy before anyone files or shares it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Redact emails, phones, national IDs, and account numbers from [PACK]. Keep matter IDs. Do not send the pack. Sources: The pack file or folder I name. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not file the pack. Do not send it to opposing counsel. Do not e-sign a cover letter. - Do not store a new unredacted copy in a shared folder. List types removed, not the raw values. Deliverable: Redacted path, types removed, leftover-risk notes, pages I must still check. Review point: I review. I share or I file.
Pro tip: Screenshots hide less than you think. Crop or blackout, then you look.
Client update the lawyer still sends
17/21✨ What it does
The Bot drafts a client update for [MATTER] from [DOCKET] and [LAST UPDATE], with status, next dates, and what you need from the client, in plain language. You verify the facts and you send the letter.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a client update for [MATTER] from [DOCKET] and [LAST UPDATE]. No invented outcomes. Do not send. Sources: [DOCKET], [LAST UPDATE], [MATTER FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send the letter. Do not file a status report. Do not copy opposing counsel. - This is not legal advice. If a date or ruling is missing from the sources, write unknown. Deliverable: Draft letter, facts cited, unknowns, what I need from the client. Review point: I verify. I send.
Pro tip: Put bad news in the first paragraph. Do not let the Bot bury a lost motion.
Never-do and roster
4 promptsLegal Bot description
18/21✨ What it does
The Bot writes a description named [NAME] with the systems it may open, the draft-only rule, and a never-file, never-serve, never-e-sign footer. You create the Bot and you paste the footer yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a legal Bot description named [NAME] with systems, the draft-only rule, and a never-file / never-serve / never-e-sign footer. Sources: [SYSTEMS], [MATTER TYPES], [REVIEW DAY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create the Bot. The footer must include do not file, do not send to opposing counsel, and do not e-sign. - This is not legal advice. Write that isolation is per user, not per Bot. Deliverable: Name, 8-line description, weekly jobs, never-do footer. Review point: I create the Bot. I paste the footer.
Pro tip: One primary job. A Bot that drafts and files is a malpractice machine.
What legal Bots never do
19/21✨ What it does
The Bot writes a never-do list from your rules, such as [NO SERVICE, NO E-FILE, NO ADVICE TO A CLIENT], plus the human substitute for each item. You paste the list into every legal Bot on this computer.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write the never-do list for legal Bots on this computer from my rules: [EXAMPLE: NO SERVICE, NO E-FILE, NO ADVICE TO A CLIENT]. Sources: My rules, the apps already on this computer: [LIST]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - This is not legal advice. The list must include do not file, do not send to opposing counsel, and do not e-sign. - Do not email this list to a client as if it were a legal opinion. Deliverable: 12 never-do items and the human substitute for each. Review point: I paste it into every legal Bot.
Pro tip: If it can click the e-file button, this list is the product.
Shared-computer privilege memo
20/21✨ What it does
The Bot writes a one-page memo that every Bot on this computer can see [MATTER FILES] and the same logins, so a second Bot is not a privilege wall. You paste the memo into each legal Bot description.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a one-page memo: this computer is shared, [MATTER FILES] are visible to every Bot, and privilege is not a second Bot. Sources: My tools: [LIST]. Matter folders already on the computer: [LIST OR UNKNOWN]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email this memo to a client. Do not file it. Do not treat a second Bot as a privilege wall. - Do not rotate logins or delete matter files. Approvals are the fence, not the Bot name. Deliverable: Memo plus 5 "this is not isolated" examples a lawyer would care about. Review point: I paste it into each legal Bot.
Pro tip: Official docs: isolation is per user, not per Bot. A "litigation-only" name is not a fence.
Monday docket routine
21/21✨ What it does
The Bot writes a Monday job at [08:00] [TZ] that pulls [DOCKET SOURCE] for open matters and posts a review table here, without filing or mailing anyone. You enable it after a clean test week.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Mondays at [08:00] [TZ], pull [DOCKET SOURCE] for open matters and post a review table here. Do not file. Do not mail anyone. Sources: Current [DOCKET SOURCE]. If the portal is down, fail. Do not reuse last Monday. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not file during the routine. Do not send anything to opposing counsel. Do not e-sign. - If the source is down or stale, report failure. Do not invent a quiet week. Deliverable: Routine card: next run, input, output, approval line, failure behavior. Review point: Test week first. I enable it.
Pro tip: Fail if the portal is down. Do not reuse last Monday's docket.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides