Demand Notice Drafter

Demand Notice Drafter

What this does

Drafts a formal demand notice: a letter that particularises a claim precisely, states exactly what compliance requires, sets an absolute deadline, and states the consequence of non-compliance only to the extent the client is actually prepared to follow through on. A demand notice is often itself evidence — of when a party had notice of a claim, of what was actually demanded — so vagueness here is a defect, not a style choice.

Before you start

The underlying facts and claim. What happened, what is owed or was breached, supplied by the user. This is blocking; the notice cannot be particularised without it.

The relief demanded, and the deadline for compliance. An exact figure or action, and an exact date — not "promptly" or "within a reasonable time." This is blocking; a demand notice with a vague deadline is a weaker document and this skill does not draft one.

Governing law. Some causes of action and forums require a demand notice as a strict precondition to suit, with mandatory minimum notice periods, required content, or specified methods of service — get this wrong and a later filing can be invalid. Extract it from any supplied documents or ask; treat compliance with any such formality as a verification point rather than something to assert from memory.

Not blocking, ask once and proceed on what is confirmed: the legal basis for the claim, if not already stated — the contract clause, the statutory provision, the tortious basis. If the user has not specified it, do not invent one; either ask, or draft the notice on the stated facts and demand without naming an unconfirmed legal basis, and say so.

Method

1. Classify the claim type in one line — breach of contract, statutory demand, tortious claim, other — before drafting anything.

2. Particularise the facts precisely. Who, what, when, and by reference to specific dates, documents, or clauses where available. A demand notice built on a vague factual recitation invites a vague response and carries less weight later.

3. State the legal basis only in the terms the user has actually supplied. Do not invent a cause of action, statute, or clause reference. Where none has been given, either ask for it or draft the notice around the stated facts and demand, and say plainly that no specific legal basis has been named.

4. Quantify the claim precisely. State the principal amount, and if interest is claimed, state the rate and its basis rather than assuming one; where the figure is not a flat sum, show the arithmetic so the calculation can be checked.

5. State the demand itself unambiguously — exactly what compliance requires (pay this sum, do or cease doing this specific thing, deliver this item) and the exact date by which it must happen. Never "within a reasonable time."

6. State the consequence of non-compliance only to the extent the client is actually prepared to pursue it. Do not draft a threat of a specific proceeding, remedy, or consequence the client has not confirmed they intend to follow through on — an empty threat weakens the notice and can be used against the sender later.

7. Flag any formal requirement the governing law may impose on this notice type — a mandatory minimum period, a required method of service, prescribed content — as a point to verify rather than a fact to assert. Do not state that the notice satisfies a statutory precondition without that being confirmed.

8. Add a service note. Remind the user to record how and when the notice is sent, since proof of service or receipt commonly matters later.

Output

1. Header. Sender/client, recipient, date, matter reference.

2. The notice. Salutation, particularised facts, legal basis (only as supplied), the quantified demand shown with its calculation where relevant, the deadline, the stated consequence of non-compliance, and a reservation of rights.

3. Service note. How to serve the notice and what to retain as proof of service.

4. Points requiring verification. Any notice-period, content, or service-method requirement under the governing law; anything resting on a legal basis the user has not confirmed.

Do not

Do not invent the legal basis, statute, or clause the claim rests on.

Do not use a vague deadline. Use an exact date.

Do not threaten a proceeding, remedy, or consequence the client has not confirmed they are prepared to pursue.

Do not assert that the notice satisfies a statutory notice-period or service requirement without that being verified — flag it instead.

Do not soften or hedge the demand into something that reads as negotiable when the client wants a firm demand, and do not draft it more aggressively than the client's actual instructions where they want room to negotiate.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: rohasnagpal
• Source: rohasnagpal/legal-ai-skills
• License: MIT

Install and usage instructions live in the source repository linked above.