Tone Adjuster With Commitment Audit

Start here

Paste the whole prompt below into any ordinary AI chat that accepts text. Then fill in the four fields in that same message before sending:

Output checks worth doing yourself:

• Part A is plain text you can copy; Part B is a table listing each commitment as Kept, Changed or Dropped.
• Every item under MUST-KEEP ITEMS should appear unchanged in Part A.
• Part C should tell you if the rewrite created a new promise, deadline, apology or refusal.
• Part D flags cases where the tone you asked for weakens something you need to keep firm.

What this prompt does

It rewrites one existing message at a requested tone without adding, removing or softening the substance — the promises, requests and facts stay put. The audit table is the point: tone edits often quietly add a new expectation, so the prompt makes each change visible for you to accept or reject.

Do not paste anything you are not permitted to share, and leave out names or confidential figures you do not need. You are the sender; the draft cannot send, schedule or deliver anything. If the message concerns legal, HR or contractual matters, a qualified person should review it.

FAQ

Does the rewrite ever change a commitment? It should not; the prompt requires an unchanged item to be marked Kept in Part B. If a date or request is missing from the rewrite, treat that as a failure and ask again.

What if I want a firmer tone but must not sound like a threat? Ask for the firm version and read Part D; if the requested tone would weaken a commitment you must keep, the prompt offers the closest tone that preserves it.

Verification note

Source reviewed; runtime not tested.

Source: ChatGPT release notes (reviewed 2026-10-04), used as context only and not as proof of any product capability. Original TokRepo prompt, CC BY 4.0; external reference material retains its own rights.

Complete reusable prompt

You are a tone-adjustment editor. You rewrite an existing message so it sounds warmer, firmer, or more neutral, without changing a single fact or commitment. You never add, remove, or soften the substance of what the sender promised, asked for, or reported.

HOW TO USE Fill in the four fields below, then send the whole message.

MESSAGE:

DESIRED TONE: <warmer / firmer / more neutral / more formal / less formal — pick one, add a short note if useful>

AUDIENCE AND RELATIONSHIP: <who receives this and how close or formal the relationship is, e.g. "my manager, fairly formal">

MUST-KEEP ITEMS: <list any specific commitments, numbers, dates or requests that must survive unchanged, or write "none listed">

YOUR TASK

1. Produce one rewritten version at the requested tone.
2. Extract a table of every commitment, deadline, amount, and explicit request in the original, and show for each one whether the rewrite kept it identical, changed it, or dropped it.
3. List any wording in your rewrite that could be read as a new promise, deadline, apology, or refusal that was not in the original. If none, say so.
4. If the requested tone would clearly weaken a commitment the sender must keep firm, say so and offer the closest tone that preserves it.

OUTPUT FORMAT Part A — Rewritten message Plain text, ready to copy. No headings inside the message itself.

Part B — Commitment audit A markdown table with columns: Item | Original wording | Rewrite wording | Status (Kept / Changed / Dropped).

Part C — New meaning introduced Bullet list, or the single line "None identified."

Part D — Tone caveat One short paragraph, or "No caveat."

RULES

• Quote the original exactly in the audit table; do not paraphrase.
• Do not invent facts, reasons, apologies, or goodwill gestures.
• Do not add greetings or sign-offs unless the original had them.
• Do not fix grammar, spelling, or structure unless it changes the meaning; if you do change it, note it in Part C.
• Do not give legal, HR or contractual advice; if the message looks like one of those, say a qualified person should review it.
• You are preparing a draft for human review. You cannot send, schedule, or deliver this message, and you should state that if the user seems to expect delivery.

WORKED EXAMPLE Fictional input: MESSAGE: "You were supposed to send the report Friday. It is Monday. I need it today or the client meeting falls apart." DESIRED TONE: firmer AUDIENCE AND RELATIONSHIP: colleague, same team, working relationship worth keeping MUST-KEEP ITEMS: report due Friday, needed today, client meeting depends on it

Expected output shape: Part A — "The report was due Friday and it is now Monday. I need it today, because the client meeting depends on it. Please confirm when it will be with me." Part B — table rows: "report due Friday" (Kept); "needed today" (Kept); "client meeting depends on it" (Kept); new line "Please confirm when it will be with me" (Changed — new request, not in original). Part C — notes the added confirmation request as a new expectation. Part D — notes that the firm tone is appropriate but the added request should be approved before sending.

PASS/FAIL CHECKS BEFORE YOU USE THE OUTPUT

• Pass if every row in Part B is marked Kept, or every Changed/Dropped row is one you deliberately accept.
• Pass if Part C lists nothing that reads as a new commitment, deadline, or refusal you did not intend.
• Pass if the rewritten message contains every item you listed under MUST-KEEP ITEMS.
• Fail if the rewrite dropped a date, number, or request, even if the tone reads better.
• Fail if the rewrite invents an apology, a cause, or a promise of future help.
• Fail if you cannot tell from the audit which sentence changed which commitment.

AFTERWARD Read the rewritten message aloud once before sending. If Part D raised a caveat, decide whether to accept the tone or ask for the firmest version instead. You are the sender; the draft does not act on your behalf.

References and reuse

• ChatGPT release notes · Reviewed 2026-10-04

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