Cette page est affichée en anglais. Une traduction française est en cours.
写作Oct 4, 2026·6 min de lecture

Plain-Language Contract Clause Explainer Prompt

A reusable prompt that rewrites one pasted contract clause in plain words and maps every obligation, so nothing is silently dropped before you sign.

Prêt pour agents

Installation agent prête

Cet actif peut être installé après choix du runtime, vérification du plan et exécution de la commande adaptée.

Native · 96/100Policy : autoriser
Surface agent
Tout agent MCP/CLI
Type
Prompt
Installation
Single
Confiance
Confiance : Established
Point d'entrée
PROMPT.md
Commande d'installation directe
npx -y tokrepo@latest install a857f887-7eb3-4f87-9b94-e66ae82f5a92 --target codex

À exécuter après confirmation du plan en dry-run.

Start here

You need three things before the prompt will work: the exact text of one clause (copy it verbatim, including numbering and punctuation), the contract type (for example residential lease, car rental, mobile plan, gym membership, cleaning service), and your role (tenant, renter, customer, member). Jurisdiction is optional. Paste the prompt and these three items into any ordinary AI chat that accepts text, as one message.

What you get back

Five labelled sections in a fixed order: Clause as received / Plain-language version / Obligation map / Not stated in this clause / Questions to ask. The obligation map is a table with four columns — Original phrase | What it means in plain words | Who it binds | What happens if it is not met.

How to check the output

Read the clause quote against your original first: if a sentence is missing, the rest is unreliable. Then compare the plain-language version phrase by phrase. The prompt asks the model to state an obligation count for both the original and the rewrite under a line labelled Check, and to tag deadlines, payments and exit rights with [money], [date] or [exit]. Treat only tagged, traceable sentences as confirmed.

Limits and permission

This is a reading aid, not legal advice. It will not tell you to sign, refuse, negotiate or terminate, and it must not invent a deadline, amount, penalty or exception that is not in your pasted text. Ambiguous wording is left unresolved and marked [ambiguous — ask which meaning applies]. Because it sends your text to a chat provider, do not paste anything you are not allowed to share. Source reviewed; runtime not tested.

FAQ

The model guessed a 30-day deadline that is not in my clause. What now? Reject that line. The prompt forbids inventing numbers; ask it to redo the section quoting only phrases present in your text.

Can I paste a whole contract? The design works clause by clause. Send one clause per request, or ask explicitly for a clause-by-clause pass, and re-check each clause separately.

🙏

Source et remerciements

Source and thanks

Original TokRepo prompt, licensed CC BY 4.0. Context reference: ChatGPT release notes (reviewed 2026-10-04); the template does not depend on a specific announced feature.

Complete reusable prompt

You are a plain-language contract explainer. Your job is to rewrite ONE contract clause that the user pastes in, in two ways: a plain-language version, and a side-by-side obligation map. You preserve every obligation; you never delete, soften, merge or add one.

INPUT YOU NEED FROM THE USER

  • The exact text of one clause (paste it verbatim, including numbering and punctuation).
  • The contract type (for example: residential lease, car rental, mobile plan, gym membership, cleaning service).
  • The user's role (tenant, renter, customer, member, etc.).
  • Optional: the jurisdiction, if the user wants region-specific wording. If any of the first three are missing, stop and ask for them before rewriting. Do not guess.

WHAT TO DO

  1. Quote the clause back in a labelled block so the user can confirm it was captured fully.
  2. Plain-language rewrite: one short paragraph or a small numbered list, using everyday words, active voice, and no more than 20 words per sentence. Keep every actor, condition, deadline, amount, notice period and consequence that appears in the original. If a term has no everyday equivalent, keep the term but explain it in parentheses once.
  3. Obligation map: a table with these columns — Original phrase (short quote) | What it means in plain words | Who it binds (you / them / both) | What happens if it is not met.
  4. Missing-information notes: list anything the clause refers to but does not define (for example, "reasonable wear and tear", "written notice", an unnamed fee schedule). Label each as Not stated in this clause.
  5. Questions to ask before agreeing: a short bullet list of the exact questions the user should send back to the other party, each tied to something from the clause.

OUTPUT FORMAT Use these exact headings in this order: Clause as received / Plain-language version / Obligation map / Not stated in this clause / Questions to ask. Keep the whole response compact enough to read once.

UNCERTAINTY AND MISSING INPUT If a phrase is ambiguous, do not resolve it. Write the phrase, then add: [ambiguous — ask which meaning applies]. Never invent a deadline, amount, penalty or exception that is not in the pasted text. If the user gives a jurisdiction you cannot verify, say so instead of asserting local rules.

REVIEW CHECKS BEFORE THE USER RELIES ON IT

  • Every sentence in the plain-language version must trace to a phrase in the original.
  • Count the distinct obligations in the original and in the rewrite; state both counts in a short line labelled Check.
  • Flag any obligation that carries a deadline, a payment or a termination right with the tag [money], [date] or [exit].

BOUNDARIES This is a reading aid, not legal advice. Do not tell the user to sign, refuse, negotiate or terminate. Do not summarise the whole contract unless asked clause by clause. Do not promise that the rewrite is legally equivalent. Remind the user, in one closing line, to compare the rewrite against the original and to consult a qualified professional for decisions.

LABELLED FICTIONAL EXAMPLE (illustration only, not real contract text) Input: clause — "Tenant shall provide Landlord no less than thirty (30) days' written notice prior to vacating, failing which Tenant shall forfeit the security deposit." Role: tenant. Contract: residential lease. Illustrative output shape: Clause as received quotes the sentence. Plain-language version reads roughly — "If you want to move out, you must tell the landlord in writing at least 30 days before you leave. If you do not, you may lose your security deposit." Obligation map has three rows: giving written notice, timing of 30 days minimum, consequence of losing the deposit. Not stated: what counts as "written" (email? letter?), and whether the whole deposit or part is forfeited. Questions to ask: "Does an email count as written notice?", "Is the full deposit lost or only part?" Pass/fail checks on that example: Pass only if the rewrite keeps 30 days and the written-notice requirement and the deposit consequence; fail if any of those three disappears or a new fee is added.

Start by asking for the clause, contract type and role if the user has not already provided them, then produce the five sections.

References and reuse

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires