Hire an AI dispute demand letter draft writer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A fact sheet of the dispute and your position
• A dated timeline with the key events marked and gaps listed
• A demand letter draft with anything unverified flagged
• A checklist for what to do after the letter is sent

How it does the job well

• Name the asset, the threat and the impact before recommending controls.
• Rank findings by real risk (likelihood and impact), with evidence for each.
• Prefer fixes that remove a problem over warnings that rely on people.
• Cite the exact law, standard or clause for compliance and legal points, and recommend qualified review.

Mistakes it avoids

• Long lists of generic issues with no evidence they apply.
• Testing or scanning systems without permission.
• Presenting a legal opinion as final.

What a good result looks like

An example, not your task: A customer, supplier or partner owes you money and has not paid.

• Fact sheet. The demand type, tone, parties, what was agreed, what went wrong, what you want and what you will do if ignored.
• Timeline. Dated events from your records with sources, key events marked, and a list of gaps and unclear dates.
• Demand letter draft. The letter itself, plus a list of items to verify and a checklist for after sending.
• Hand-back summary. Each step's file, any step not run, and every MISSING line in one list.

How the work is checked

• Each step passed its own checks, or the run stopped at the step that failed and says why.
• The steps ran in order, and each one used the result of the one before.
• Nothing was invented to fill a gap. Every gap is a MISSING: line.
• Nothing was sent, published or paid for without a clear yes.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Gather the facts of the dispute. Asks what kind of demand it is, the tone, the reply window and the signer, then records the parties, what was agreed, what went wrong, what you want and what you will do if ignored.
• Build a dated timeline from your emails. Reads your emails and documents, pulls out each dated event, merges repeats, marks the ones that matter and lists the gaps. Use it to correct the fact sheet.
• Draft the demand letter. Writes the letter from the fact sheet and the timeline, after a check for privileged facts, admissions and settlement marking. It flags any quote or date it cannot match.
• Pause for a lawyer. Have a qualified lawyer read the letter before it goes out. This workflow gives a first draft, not legal advice.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id turn-a-dispute-into-a-checked-demand-letter-draft only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/turn-a-dispute-into-a-checked-demand-letter-draft/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Answers about the dispute, such as who, what was agreed and what went wrong
• What you want and what you would accept
• Your emails, contracts and invoices about it
• The tone you want and who will sign (asked by the workflow)

Functions and deliverables

• Dispute demand letter draft writer: Share the dispute, agreement and supporting messages. Get a fact sheet, a dated timeline and a demand-letter draft for a lawyer to review.
  • A fact sheet of the dispute and your position
  • A dated timeline with the key events marked and gaps listed
  • A demand letter draft with anything unverified flagged
  • A checklist for what to do after the letter is sent
• Demand letter fact gatherer: Answer structured questions about a dispute. Get a reviewed fact sheet, open risks and a handoff to letter drafting.
  • Completed fact sheet
  • Posture notes: tone, deadline, marking
  • Evidence and gaps list
  • File ready for the drafting step
  Source: Anthropic.
• Dispute timeline builder: Build a dated dispute timeline from documents. Get source links, key events, gaps and first-pass flags for legal review.
  • A dated timeline with sources
  • Events marked by importance
  • A list of gaps and missing documents
  • A version history when you update it
  Source: Anthropic.
• Demand letter drafter: Share a completed dispute intake. Review legal and factual risks, then get a letter draft and checklist for attorney review.
  • Demand letter draft
  • Pre-draft risk check
  • Word file
  • Post-send checklist
  • Notes on quotes to verify
  Source: Anthropic.
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• A customer, supplier or partner owes you money and has not paid.
• Someone broke an agreement and you want to put it on record.
• You need a clear, calm first letter before a lawyer gets involved.

Limits to check before starting

• You have a large claim or a lawyer already on the case: go to your lawyer first, and bring the fact sheet and timeline.
• You only need to chase one late invoice politely: send a short reminder email yourself.
• You want a ready-to-send letter with no review: this gives a first draft, so ask a qualified lawyer to read it.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It holds HANDOFF.md and the 3 skill files in the order they run: Demand letter fact gatherer, Dispute timeline builder and Demand letter drafter.
• Give the folder to Claude, in Claude Code or as files in a Claude Project. Say "Follow HANDOFF.md". It needs a tool that can read files.
• Answer its questions in full. Add your emails, contracts and invoices when it asks.
• Check the timeline. Every date and amount in the letter should match a record in it.
• Read every item marked verify before you do anything else.
• Ask a qualified lawyer to read the letter before it is sent.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/turn-a-dispute-into-a-checked-demand-letter-draft for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.