Statement Of Claim Drafter

Statement of Claim Drafter

Purpose

Produce a coherent merits pleading in which every material allegation advances an identified claim, every claim connects to evidence and law, and every item of relief follows from the pleaded case and quantum record.

Required inputs

Obtain the arbitration agreement, complete contract set, notice or request for arbitration, tribunal and institutional details, procedural orders, governing substantive law, factual instructions, source documents, prior correspondence, claimed heads of loss, calculations, payments, mitigation evidence, and requested relief.

Ask for the filing deadline, page or format limits, status of document production, witness and expert plans, interest basis, currency, tax treatment, and whether amendment or reservation of unquantified claims is permitted.

Do not draft final factual allegations without a source record. Where instructions are incomplete, create an allegation-evidence-gaps table first and use explicit placeholders in the pleading.

Method

1. Build a claim architecture before writing prose: jurisdictional basis, parties, transaction, chronology, each cause of action, elements, material facts, evidence, causation, loss, defence anticipated, and relief.
2. Establish jurisdiction and admissibility without overstating them. Plead consent, scope, party status, conditions precedent, commencement, and tribunal constitution; identify any known objection.
3. Draft a disciplined chronology. Separate agreed background, claimant's allegations, contemporaneous documents, respondent statements, and inference. Use exact dates and defined terms consistently.
4. Plead each claim separately. State the duty or obligation, legal or contractual source, conduct constituting breach, attribution, causation, and remedy. Retrieve and cite current authoritative law when legal propositions are required.
5. Particularise allegations that demand specificity under the applicable procedure. Do not use labels such as fraud, bad faith, wilful misconduct, or repudiation without the facts said to establish them.
6. Build quantum by head of claim. Show formula, inputs, currency, valuation date, source, causation, mitigation, avoided cost, set-off treatment, and uncertainty. Reconcile the narrative, schedules, and total.
7. Plead declarations, payment, performance, termination consequences, interest, and costs separately. Identify the legal or contractual basis and avoid relief beyond the tribunal's apparent jurisdiction.
8. Anticipate only material defences supported by the record, such as limitation, waiver, variation, force majeure, contributory conduct, contractual caps, exclusion, set-off, or failure to mitigate. Plead responsive facts without turning the claim into a reply.
9. Create a citation and exhibit map. Ensure every quotation and material figure matches the source and every cited exhibit exists.
10. Run consistency checks across the notice, claim, contract, defined terms, chronology, figures, prayers, and annexes. Identify amendments that may require permission.

Output

Produce:

1. Statement of claim — introduction, parties, jurisdiction, facts, claims, quantum, and relief.
2. List of exhibits and authorities.
3. Claim-evidence matrix — element, pleaded fact, source, witness, and gap.
4. Quantum schedule — head, formula, inputs, evidence, and total.
5. Verification list — unresolved facts, law, figures, permissions, and procedural requirements.

Guardrails

• Do not invent facts, admissions, quotations, documents, authorities, calculations, or service events.
• Do not conceal documents or facts that materially qualify the pleaded account.
• Do not equate an asserted loss with recoverable damages without proving causation and the governing measure.
• Do not reserve every conceivable claim generically; identify what is genuinely unquantified or dependent on later material.
• Maintain privilege and confidentiality labels and avoid pleading settlement communications without confirming admissibility and waiver.

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.