agentleFS
SprintlawSprintlaw/legal-skills/skills/draft-contract/SKILL.md

draft-contract

Skill0 starsChanged 31 days agoMITView on GitHub

Draft a contract, deed, terms and conditions or policy for one side to Sprintlaw house standard, then check it the way a senior lawyer would before it goes out. Takes a brief, writes a plan mapping every brief point and checklist item to a clause, drafts from the best starting point (the user's precedent, then house clause patterns), runs the doc-audit script, self-reviews against the document-type checklist and a consistency pass, stress-tests with scenario-test and, for high stakes, adversarial-review, then delivers a .docx with assumptions and every [insert] item listed. Also edits existing documents with minimal changes. Use for "draft", "write me a", "prepare an agreement", "template", "terms and conditions", "services agreement", "contractor agreement", "shareholders agreement", "NDA", "deed of variation", "amend this agreement", "redraft clause", "put this in house style", in Australia, the UK, New Zealand or the US.

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 14 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run it inside sprintlaw-mode (playbook PB3) or on its own.

    line 15
  2. Distinctive:

    The brief wins: Every instruction in the brief has a clause.

    line 19
  3. Distinctive:

    Nothing in the document that is not for signing: No drafting notes, options, "[confirm]" or alternative clauses inside it.

    line 23
  4. Distinctive:

    No law from memory: Use the jurisdiction pack for conventions and mandatory content.

    line 24
  5. Distinctive:

    Cross-references by number, checked: Never guessed, never "the relevant clause".

    line 25
  6. Very specific:

    Write plan.md before drafting a word of the document.

    line 70
  7. Very specific:

    The client's or user's own precedent: Keep its structure, defined terms and style.

    line 91
  8. Distinctive:

    Follow references/house-style.md.

    line 99
  9. Distinctive:

    Write long documents section by section.

    line 111
  10. Distinctive:

    Read the rendered document, not your memory of it.

    line 123
  11. Distinctive:

    Keep the document's own style, numbering, defined terms, definition placement and voice, even where house style would differ.

    line 152
  12. Distinctive:

    [insert] items: every placeholder the client must fill, by clause.

    line 175
  13. Distinctive:

    No commentary inside the document.

    line 179
  14. Distinctive:

    Does not give advice on whether the deal is a good one.

    line 183
  15. Distinctive:

    Does not invent facts, prices, entity details or law.

    line 184
  16. Distinctive:

    Does not draft where a regulated form, mandatory disclosure document or registered instrument is required (for example franchise disclosure …

    line 185
  17. Distinctive:

    Does not file, lodge, sign or send anything.

    line 186

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Draft contract

A first draft from a model usually reads well and fails quietly: a brief point with no clause, a survival list pointing at the wrong numbers, a cap that swallows the indemnity, a statute from the wrong country, an execution block for the wrong kind of entity. This skill drafts the way a careful senior lawyer does: plan first, draft from proven wording, then check mechanically, against a checklist, against the brief, against real-world scenarios and against a hostile reader before anyone sees it.

Run it inside sprintlaw-mode (playbook PB3) or on its own.

Non-negotiables

  • The brief wins. Every instruction in the brief has a clause. Where the brief departs from the market default (a licence, not an assignment; no restraint), follow the brief and say so in the reply.
  • Lean to our client, within what the other side would sign. Every discretionary position (caps, carve-outs, termination rights, restraints, indemnities, payment terms) favours the client, but stays commercially normal and inside any unfair terms or consumer regime that protects the counterparty. Overreach gets struck out or stalls the deal.
  • Never invent identity facts. Names, entity numbers, addresses, dates and prices you do not have are [insert …]. A person the brief names only by role is [insert Founder 2 full name], never a made-up name.
  • Commercial mechanics get defaults, not blanks. Notice periods, cure periods, payment terms, caps, restraint periods and thresholds get a sensible default written in and flagged as an assumption in the reply.
  • Nothing in the document that is not for signing. No drafting notes, options, "[confirm]" or alternative clauses inside it. Those go in the reply.
  • No law from memory. Use the jurisdiction pack for conventions and mandatory content. Cite a statute in the document only if it is verified. Tag legal propositions in the reply.
  • Cross-references by number, checked. Never guessed, never "the relevant clause".
  • Minimal change when editing an existing document.

Step 1. Brief intake

Get these from the brief, the conversation and any documents first. Ask for what is missing in one message, grouped, at most six questions (drafting needs more facts than a review; group them so the user can answer in one reply). Then proceed on stated assumptions.

ItemCaptureIf missing
PartiesLegal names, entity types, identifiers, addresses, who signs; trading names[insert]; ask about entity type if it changes execution
Our client and sideWhich party, and what role (supplier, customer, employer, founder)Ask. Do not draft without it
The dealWhat is supplied or agreed, for how much, for how long, deliverables, milestonesAsk for the core; default the mechanics
JurisdictionGoverning law; where each party is; whether any customer, worker or user is a consumer or employee elsewhereAsk. Do not draft without it
Commercial variablesPrice and payment terms, term and renewal, exclusivity, IP model (assignment or licence), cap, restraint, termination rightsDefaults from references/clause-patterns.md, flagged
Must-haves and fearsDeal-breakers, the outcome the client most wants to avoidThe family checklist's priorities
FormSigned agreement, deed, click-through terms, master agreement with statements of work, amending documentInfer from the family; ask if it changes the structure
Starting pointThe client's own precedent or template, the counterparty's form, nothingHouse patterns
Output.docx (default), a Word template to build on, markdown.docx

Gate: if you cannot tell the document type, our client's side or the governing law, stop and ask. Everything else can be assumed and flagged.

Step 2. Pick the family and the form

Name the family before planning. Drafting the wrong kind of document well is still a failed draft.

FamilyWatch for
Services or master services agreementSigned terms, reusable standard terms, or master agreement plus statements of work? Industry modules (health, trades, creative, IT, logistics)
Contractor agreementIndividual or company; independence; key person; IP; statutory contribution risk. Run employment-check if it looks like employment
Employment agreementEmployment type, minimum entitlements, any industry instrument. Run employment-check for entitlements
NDA or non-disclosure, non-use and non-circumventionMutual or one-way, purpose, overseas counterparty
SaaS or platform termsSigned or click-through; customer type; data and AI features
Website, ecommerce or marketplace termsRoute with the table in the online terms playbook before drafting
Privacy policy, cookie notice, processing termsUse privacy-compliance
Supply, manufacturing, distribution, hireTitle and risk, specification, territory and exclusivity, minimums
Shareholders or founders agreementUse business-setup for structure decisions; usually a deed
IP assignment or licenceAssignment or licence; deed if consideration is nominal or past; use ip-brand for ownership questions
Business or share saleUse business-sale
LeaseUse lease-review
AmendmentDeed of variation, amending agreement, or a clean amended and restated agreement? Identify the original by title, date and parties

Deed or agreement: in markets that use deeds, use a deed where there is no fresh consideration (variations giving something for nothing, releases, past IP assignments), for guarantees, and where the house checklist says so (shareholders, IP assignment deeds, accession deeds). In the US, deeds are generally not used for contracts: recite and provide consideration instead. Read the pack's conventions.md for deed formalities before writing the execution page.

Step 3. Write the plan

Write plan.md before drafting a word of the document. It is the contract between the brief and the draft.

# Plan: <document> for <client> (<side>), <governing law>
## Brief map
| # | Brief point (quoted or paraphrased) | Clause or schedule that carries it |
## Checklist map (general list + the family list in references/checklists.md)
| Item | Clause | included / excluded because <reason> / assumption |
## Defaults chosen
| Mechanic | Default | Why |
## [insert] items
## Law to check (pack files and the points to verify)
## Outline (clause headings in order, then schedules, then execution)

Gate: a brief point with no clause is a failed draft, however polished the rest. For a long document or a thin brief, show the outline and the assumptions to the user before drafting, unless they asked for a straight draft.

Step 4. Choose the starting point

In this order:

  1. The client's or user's own precedent. Keep its structure, defined terms and style. Run doc-audit on it first; precedents carry stale law, dead cross-references and remnants from other matters.
  2. House clause patterns in references/clause-patterns.md, assembled to the plan.
  3. From scratch, following references/house-style.md.

A precedent from another country goes through jurisdiction-adapt before it is used. Do not blend several precedents clause by clause; pick one spine and borrow clauses into it. If the deal must be on the counterparty's paper, this is a review job: use contract-review.

Step 5. Draft

Follow references/house-style.md. The rules that most often decide quality:

  • Structure: title; Parties; Background; Agreed terms; clause 1 Definitions and interpretation; operative clauses; boilerplate; schedules (Key Details first); execution. Online terms use the click-through structure instead.
  • Variables live in the schedule. Price, term, deliverables, milestones, caps and special conditions go in Key Details; the body refers to them by name and never restates them. Governing law, notices and execution never go in Key Details.
  • Definitions alphabetical, each capitalised term defined once and used, no obligations hidden in definitions.
  • Plain English: "must" and "must not", present tense, active voice, short sentences, spelling for the jurisdiction.
  • Lists: a lead-in ending in a colon, items ending in semicolons, "; and" or "; or" on the second last, a full stop on the last. Never a single lettered item on its own.
  • Cross-references: "clause 14 (Termination)" in survival and precedence lists. Never typed from memory: check them against the rendered numbering.
  • Lean to the client as set in the plan, and write down each position the other side may resist for the reply.
  • Execution blocks matching each party's entity type and the pack's conventions.md. Unknown counterparty entity type: an authorised signatory block, not an assumed company formality.
  • Statements of law inside the document (consumer rights savings, mandatory notices) come from the pack, verified, in plain words.

Write long documents section by section. If the output is chat rather than a file, deliver it in numbered parts and continue on request, so nothing is dropped.

Step 6. Run the integrity script

python3 ../doc-audit/scripts/docaudit.py <draft file> --jurisdiction <au|uk|nz|us>

(Relative to this skill's folder; find doc-audit/scripts/docaudit.py if installed elsewhere.) Fix every error. Check every warning and leave only those you can justify. Run it again until clean. Send the "Authorities to verify" list to cite-check.

Step 7. Self-review

Read the rendered document, not your memory of it.

  1. Brief compliance. Walk plan.md line by line: every brief point carried, every checklist item included, deliberately excluded or listed as an assumption.
  2. Checklist. The general list and the family list in references/checklists.md.
  3. Consistency pass in the same file: term, periods and survival; dispute path and governing law; cap, exclusions, indemnities and carve-outs; policies; termination and payment; restraints proportionate to the person; parties and execution blocks.
  4. Read it as the other side's lawyer. Mark anything they will strike as overreaching, and anything a court or regulator would strike. Pull back the overreach or list it as "likely pushback" for the reply.

Fix the source and rebuild rather than patching the output, so the audit and the document cannot drift apart.

Step 8. Scenario test

For anything material (the deal matters to the client, runs longer than a year, involves exclusivity, equity, IP the business depends on, a restraint or a guarantee), run scenario-test on the draft with six to ten scenarios, including the client's stated fear and one success scenario. Fix every Gap and Conflict in the draft and re-run the affected scenarios. Report what was tested and changed.

Step 9. Adversarial review

Run adversarial-review when the document will be signed or relied on and the stakes justify it: shareholders and founders documents, sales, franchises, high-value commercial deals, consumer terms that will be published, anything the client will use without a lawyer reading it, or when the user asks. Loop until PASS. After three rounds, stop and report what remains.

Step 10. Deliver

  1. Build the .docx. Use, in order of preference: the docx skill; python-docx building from the client's or a house template with real heading and list styles; pandoc draft.md -o draft.docx (with --reference-doc=<template.docx> when a template exists); markdown only when nothing else is available. Use real Word numbering where you can; if you type numbers into the text instead, check every cross-reference against the final numbering.
  2. Re-run doc-audit on the final .docx.
  3. Name the file for the reader: "<Document title> - <Party A> and <Party B>.docx".
  4. Reply per the contract below.

Mode: editing an existing document

The minimal-change rule:

  • Change only what the instruction requires, plus the consequential changes needed to keep the document consistent (definitions, cross-references, survival and precedence lists, schedules, execution).
  • Keep the document's own style, numbering, defined terms, definition placement and voice, even where house style would differ. Fix spelling only where it is wrong for the jurisdiction.
  • Restyling never silently changes substance. If a house-style rewrite would alter meaning, keep the meaning and flag the tension.
  • Flag any shift in risk the requested edit causes, separating what must be fixed from judgment calls.
  • List every cross-reference your edits changed.

Output, in order of preference:

SituationDeliver
The user has a .docx and wants it backTracked changes on their original file via redline (formatting survives; each change has a comment)
Specific edits, no file or a PDFAn amendment list: clause, short quote of the current words, replacement wording, one-line reason
Structural rewrite (reordering, merging, renumbering)A full redraft, after telling the user that a rebuilt file loses the original formatting unless it is compared against the original
Short document, or the user asks for a clean versionFull redraft

Amending documents: identify the original agreement (title, date, parties), the exact clauses changed (quote old and new), the effective date, that everything else continues unchanged, consideration or deed form, and execution by the same parties.

Reply contract

The reply contains, in this order:

  1. What it is: two lines on what the document does, for whom, under which law, and the file path.
  2. Positions taken for the client: three to six bullets, each marked "likely pushback" where the other side may resist.
  3. Assumptions and defaults: each with the value chosen ("Payment: 14 days from invoice").
  4. [insert] items: every placeholder the client must fill, by clause.
  5. Decisions for the client: options you closed in their favour that they may want the other way (for example single-trigger vesting acceleration), tagged [judgment].
  6. What was checked: doc-audit result, checklist and consistency pass, scenario test summary, adversarial review verdict, and any [unverified] law still to confirm.

No commentary inside the document. Offer the next step in one line (a tracked-changes version for the other side, a scenario test, a plain-English summary for the client).

Limits

  • Does not give advice on whether the deal is a good one; it drafts what the client has decided and flags risk.
  • Does not invent facts, prices, entity details or law.
  • Does not draft where a regulated form, mandatory disclosure document or registered instrument is required (for example franchise disclosure documents, regulated consumer credit or financial product documents, land transfers) without the pack's area file and a lawyer's review.
  • Does not file, lodge, sign or send anything.

When a human lawyer would help, say so in one line using the market's wording in sprintlaw-mode referral lines. Australia: Sprintlaw is an Australian law firm offering fixed-fee legal services (sprintlaw.com.au). UK: Sprintlaw UK is a legal consultancy, not a law firm (sprintlaw.co.uk). New Zealand: Sprintlaw NZ is a legal consultancy, not a law firm, whose work is done by Australian-qualified lawyers, and it does not handle leases, buying or selling a business, conveyancing, relationship property, or court and tribunal matters (sprintlaw.co.nz). US: Sprintlaw Tech LLC is a technology platform, not a law firm; legal services are provided by licensed US lawyers at ElevateNext US, LLC through the Sprintlaw platform (sprintlaw.com).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.