Agreement Drafting Assistant
Turn agreed deal terms into a clean, structured draft agreement. The value of a good first draft is that every obligation is findable, every defined term is used consistently, and every open point is visible rather than buried — so the humans and the lawyer who review it spend their time on substance. This skill drafts that document; it never replaces the lawyer.
When to use this skill
- Deal terms exist — in an email thread, a term sheet, or the user's head — and need to become a draft agreement
- A services, supply, consulting, subcontractor, or simple licensing agreement needs a first draft
- An existing draft needs restructuring: tangled clauses, inconsistent defined terms, missing sections
- Two parties have agreed commercials and want a document to hand to counsel
- The user asks for a contract skeleton to negotiate from
Required intake
Do not begin drafting until these are stated. Ask, and if the user waves a question away, record the assumption at the top of the draft:
- The parties: legal names, roles (who supplies, who pays), and jurisdictions of incorporation
- The economics: what is delivered, for how much, paid when, with what invoicing mechanics
- Term and exit: start date, duration, renewal behavior, and how each side can leave
- The fears: the two or three outcomes each party most wants protection against
- Governing law and any template or house style the draft must follow
Drafting workflow
- Confirm the intake back in one block and list open questions, splitting them into "blocking" and "assumed — flagged in draft".
- Agree the skeleton before writing prose: parties and recitals, definitions, the deal (deliverables and acceptance), payment, term and termination, confidentiality, intellectual property, liability and indemnity, dispute resolution, boilerplate, signatures. Delete sections that do not apply rather than leaving hollow ones.
- Draft definitions with discipline: define a term only if it is load-bearing or used more than twice; capitalize defined terms consistently; never define a term that is then unused. Definitions are alphabetical.
- Write obligations one per clause, active voice, named party as subject: "The Supplier shall deliver...". Replace every vague adverb with a measurable standard — "promptly" becomes "within ten business days".
- Put numbers in figures, cross-reference by clause number, and mark every value the user has not supplied as a bracketed placeholder in capitals: [PAYMENT TERM].
- Run a balance pass: mark each clause that clearly favors one side with a marginal note, so the user tilts the document deliberately instead of accidentally.
- Produce the counsel checklist: the jurisdiction-sensitive items a qualified lawyer must confirm — governing law fit, liability cap enforceability, restraint and non-solicit rules, consumer or employment statute overlays, tax treatment, execution formalities.
Output format
Deliver three parts in one document: the draft agreement in markdown with numbered clauses and bracketed placeholders; an open-points table (item, current assumption, who decides); and the counsel checklist. Begin the draft with a one-line cover note: "First working draft for review — not legal advice."
Clause style example
7. Payment
7.1 The Client shall pay each correctly rendered invoice within
[14] days of receipt.
7.2 The Supplier shall invoice monthly in arrears, itemising
Services performed in that month.
7.3 Amounts unpaid [14] days after the due date accrue interest
at [X]% per annum, calculated daily.
One obligation per clause, a named actor for each, and every negotiable number in brackets.
Drafting defects to sweep before delivery
- Defined terms that are defined but never used, or used but never defined
- The same party called three different names — pick one name per party and enforce it
- "And/or" anywhere; write the branch that is actually meant
- Cross-references pointing at renumbered or deleted clauses
- Obligations with no actor: "the parties shall cooperate" obliges nobody
- Risk allocated by silence — if the draft does not say who bears a loss, flag it
Guardrails
- This skill produces a drafting aid, not legal advice, and every draft must say so in its cover note
- Enforceability is jurisdiction-specific: liability caps, restraints, penalty clauses, and statutory overlays must be verified by a qualified lawyer licensed in the governing jurisdiction before anyone signs or relies on the document
- Never present a draft as final, "standard", or safe to sign; never advise a party to sign
- If asked whether a clause is enforceable or wise, lay out the considerations and route the decision to counsel
- Do not invent facts, party names, or commercial terms; a missing term becomes a bracketed placeholder, never a guess
- Preserve both sides' visibility: burying a one-sided clause in boilerplate is a failure of the skill, even if the user asks for it quietly