ThomasMoreAI/legal-skills-open / au/general/skills/legal-writing-mblauberg
legal-writing-mblauberg
VerifiedUse for drafting, reviewing, condensing, or source-checking Australian legal documents (forms, affidavits, submissions and orders), legal decision overviews, or correspondence. Not for academic, engineering, or general prose; use its specialist.
references/deeds-and-agreements.md
View on GitHub# Deeds And Agreements
Use this reference for transactional drafting: agreements, deeds, variations,
releases, settlement deeds, guarantees and undertakings. It supplies no current
law and no clause library. Australian execution and formality rules differ by
instrument type, jurisdiction and party type, and must be verified against the
current source before execution.
## Deed Or Agreement
Choose deliberately, because the choice changes formalities, enforceability
and limitation exposure.
| Question | Agreement | Deed |
|---|---|---|
| Does it need consideration? | Yes | No |
| How is it executed? | Signature, and the formalities the party type requires | The formalities the applicable deeds law requires, including any sealing, delivery and attestation rule |
| Limitation period | The shorter contract period in that jurisdiction | Often longer; verify the applicable limitation Act |
| Typical use | Ordinary commercial bargains | Releases, guarantees, obligations given without consideration, security and settlement instruments |
Signal the choice in the document itself. A deed says it is a deed, uses deed
language in the execution blocks, and is dated as a deed. An instrument that
calls itself a deed but executes like an agreement contains a live defect, not
a labelling quirk. Do not switch an instrument between forms during a rewrite.
## Structure
Use this order unless a template or counterparty precedent controls:
1. Title naming the instrument type and subject.
2. Date line, or a statement that the instrument is dated as executed.
3. Parties, each identified by full legal name, entity number where one exists,
and address; check whether the party is a company, a trustee acting in that
capacity, a partnership, an individual or an unincorporated body.
4. Background or recitals: verified context only, with no operative effect.
5. Defined terms, in one section, each used consistently afterwards.
6. Operative clauses, grouped so obligations sit near their triggers.
7. General clauses: governing law and jurisdiction, notices, variation,
assignment, entire agreement, severance, counterparts, costs, GST and
confidentiality.
8. Execution blocks matched to each party type.
9. Schedules and annexures, each cross-referenced from an operative clause.
## Drafting Conventions
- Use `must` for an obligation. Reserve `may` for a genuine discretion and `is
entitled to` for a right. Avoid `shall` unless a template or counterparty
precedent forces it, and then use it consistently.
- One obligation per clause. Name the actor, the act, the object and the
timing or trigger, in that order.
- Define a term once, capitalise it consistently, and never use a defined term
in a sense the definition does not carry.
- Use dates in day-month-year form. Prefer a named commencement event over a
bare date where the parties cannot control the date.
- State periods precisely: business days or calendar days, the place whose
calendar governs, and whether the period is inclusive.
- Keep money exact: the amount, the currency, whether it includes GST, and when
it is payable.
- Number clauses so each obligation has a citable address. Check every internal
cross-reference after any renumbering.
- Do not use recitals to create an obligation. If it must bind, move it into an
operative clause.
## Boilerplate Has Effect
General clauses are not filler, and cutting them for concision changes the
bargain. Before removing or shortening one, identify what it does:
- **Governing law and jurisdiction**: which law applies and where disputes are
heard.
- **Notices**: how a party gives valid notice, and when notice is taken to be
received.
- **Variation**: whether a change must be in writing and signed.
- **Entire agreement**: which pre-contract statements survive.
- **Assignment and novation**: who may transfer rights or obligations.
- **Severance**: what happens if a clause fails.
- **Counterparts and electronic execution**: whether separate signed copies and
electronic signatures are effective for this instrument and these parties.
- **Costs, interest and GST**: who pays what, and on what basis.
## Execution
Verify, do not assume:
- individuals: signature, and whether the instrument or jurisdiction requires an
independent witness;
- companies: the execution route the Corporations Act allows for that company,
including sole director and officer combinations, or execution by an agent
under a properly granted authority;
- attorneys: the power of attorney's currency, scope, registration and any
conflict restriction;
- trustees: capacity wording, the trust deed's power to enter the instrument,
and any consent requirement;
- guarantors: any independent advice, warning or witnessing requirement; and
- electronic execution: whether it is available for this instrument, this party
type and this jurisdiction on the date of execution.
Never draft an execution block by copying one from a different party type.
## Review Pass
When reviewing rather than drafting, extract each obligation into a table before
commenting: obligation, obliged party, trigger, deadline, consequence of breach,
and the clause number. Then check that:
- every obligation has an owner, a trigger and a consequence;
- every defined term is defined once and used consistently;
- every schedule is referenced and every reference resolves;
- payment, termination, liability and dispute clauses agree with each other; and
- the recitals match the operative terms and the verified facts.
Report an ambiguity as an ambiguity. Do not silently choose a reading, and do
not repair the other side's drafting error in a way that changes the commercial
position without instruction.
## Completion Gate
A transactional instrument is not finished when the prose is clean. Confirm
party identity and capacity, verify the execution route, render the final
document, resolve every placeholder, and obtain qualified review before
execution. Signing, exchanging, dating, stamping and lodging are separately
authorised acts.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |