Skip to content

ThomasMoreAI/legal-skills-open / au/general/skills/legal-writing-mblauberg

legal-writing-mblauberg

Verified

Use 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/legal-concision-and-anti-ai.md

View on GitHub
# Legal Concision And Anti-AI Drafting

Use this reference for any `draft`, `rewrite`, `condense`, `diagnose` or `final-scrub` task involving court
forms, affidavits, submissions, orders, chronologies, correspondence or annexure notes.

Load the `natural-writing` skill first for the doctrine this file does not
restate: the tiered artefact/density/structural sweep and the shared condense
procedure and integrity check. This file is the
legal-specific overlay: the Legal Function Test (a distinct classification
scheme, not the hub's observed/inferred claim schema), legal noun-stack
examples, and the leave/interlocutory register and persuasive-strength
material that has no general-prose or engineering/academic equivalent.

## Principle

Concision in legal drafting means every sentence does legal work. A sentence should state relief, a request, a
source-backed fact, a rule, a contention, a procedural step, a limitation, a safety qualification, a consequence
or a necessary transition. If it does none of those things, cut it or move it to the document that owns it.

Plain language is not casual language. Keep legal terms of art, source anchors, defined terms, forum labels,
redaction limits and honest negatives where they do work.

Cutting repetition is a persuasion move, not housekeeping (the rationale and the one-allowed-echo rule live in
`references/argument-structure-and-paragraphing.md`, which owns argument architecture: one point per paragraph,
headings that carry the argument, grounds selection, adverse authority, reply craft).

## Mode Selection

- `draft`: organise the material by legal function before writing full prose.
- `rewrite`: preserve meaning, anchors and legal status while making the passage clearer.
- `condense`: shorten first; add only if a missing source, qualification, correspondence protection,
  enforceability detail or safety fact must be stated.
- `diagnose`: report the highest-risk writing defects first, with concrete repairs.
- `final-scrub`: make one adversarial pass for overclaim, missing source, wrong home, unsafe disclosure,
  machine rhythm, noun stacks, false transitions and unsupported legal conclusions.

## Legal Function Test

For each paragraph, name its one function in a phrase:

- relief or order sought;
- procedural step;
- source-backed fact;
- legal rule;
- contention;
- consequence or prejudice;
- safety or redaction limit;
- practical request or deadline;
- correspondence protection, including an offer term, non-admission, non-waiver wording or rights reservation;
- enforceable order detail, including actor, act, object, deadline or trigger.

If the paragraph has no function, cut it. If it has two unrelated functions, split it. If another document owns
the function, move it rather than rephrasing it in place.

## Condense Pass

Follow the hub condense procedure (measure, lock invariants, reverse-outline,
de-duplicate to one home, cut fluff, narrow-not-soften, stop rule, report the
delta). Legal-specific application:

- **Lock invariants**: facts, dates, amounts, parties, source anchors, exhibit labels, rule numbers, defined terms,
  disputed-status wording, redaction limits and user-authority conditions.
- **Put the operative point first**: relief, request, answer, contention or next step.
- **Reverse-outline** the paragraphs by legal function (see the Legal Function Test above), not by the hub's
  generic paragraph test.
- **Move detail**, do not delete it, into chronologies, annexure indexes, affidavits or submissions where that
  document owns it.
- **Stop rule addition**: stop when the next cut would remove a source anchor, party label, legal status,
  redaction qualification, exhibit label, paragraph/page/line reference, forum wording or safety boundary.
- **If the revised passage is longer than the original**, run the Legal Function Test again. Keep the addition
  only if the draft was legally incomplete without it.

There is no percentage target for court work. A short filing can already be tight. A long AI-drafted passage may
need heavy cutting, but the stop rule controls the cut.

## Legal Noun Stacks

See the hub taxonomy's Noun-stacking and nominal compression for the general
repair method (cap premodifiers, unpack vague heads, prefer a verb, release
nominalisations, reuse the fix). Dense noun stacks are a common machine tell
in legal drafting because they hide the actor, act and consequence; do not
strip legal terminology, lighten the phrase around it. Legal-specific
abstract heads to replace: `context`, `framework`, `posture`, `material`,
`position`, `issue` and `risk` become the act, source, order, request,
prejudice or consequence.

| Weak stack | Better legal phrasing |
|---|---|
| `multi-forum procedural consequence context` | `The earlier order matters here because ...` |
| `source-boundary filing-facing assertion risk` | `The draft would overstate the source if it said ...` |
| `family-violence safety-context material` | `The dated safety document is relied on as context only.` |
| `protected-address disclosure framework` | `The draft asks the Court to manage address disclosure.` |
| `document-function boundary issue` | `The paragraph argues the point, so it belongs in submissions.` |

## Additive Drafting

See the hub taxonomy's Additive drafting for the general concept. Legal
application: before adding a sentence, ask what new legal function it serves
(see the Legal Function Test). If the answer is only `more background`,
`additional clarity` or `context`, cut it or move it. `makes it more
persuasive` is also a failed reason unless the addition adds a source, rule,
contention or relief.

Replace additive openers with the real legal relation:

| Empty opener | Repair |
|---|---|
| `Moreover` | state the next source-backed fact, or omit the opener |
| `Furthermore` | `The consequence is ...` |
| `Additionally` | `The prejudice is ...` |
| `In addition` | `The source shows ...` |
| `Having regard to the above` | `For that reason ...`, if the reason was just stated |

Never open consecutive paragraphs with additive adverbs. If the paragraphs are independent, no transition is
needed. If they are linked, name the link.

## Positive Form Without Spin

See Positive form is not positive spin in the hub taxonomy for the general
rule. Use positive form to make the legal position direct. Do not convert an
honest absence into reassurance.

| Weak or indirect | Better where accurate |
|---|---|
| `does not include the source document` | `excludes the source document` |
| `is not treated as proof of service` | `is relied on as transmission and actual-notice proof only` |
| `does not seek to avoid disclosure` | `seeks court-managed disclosure` |
| `is not a court order` | keep this if the absence of an order is the point |
| `does not admit liability` | keep this if non-admission is the legal status |
| `is not relied on to prove the underlying allegation` | keep this if non-reliance defines the evidentiary boundary |

Positive form is a style rule, not a licence to soften. Keep negatives for non-service, non-filing,
non-payment, non-admission, no order, no finding, no concession, no current authority, inability to reconcile
and any issue that remains under appeal or disputed.

## Defensive Over-Qualification

See the hub taxonomy's Defensive over-qualification for the general
cut-or-keep test. Legal symptoms:

- a sentence that first states what the party does not say, then what it does say, then how little it puts the
  point (`X does not assert he was 'ordered' or 'forced'; the records are silent as to motive; X asserts none
  and puts it no higher than ...`);
- belt-and-braces recitals that re-list everything left legible after a redaction, or every order a relief is
  not seeking, when one clean statement carries the limit;
- closers that re-soften a point already made (`the records cut both ways`, `to that extent the matters are
  not in contest`, `this is neither admitted nor answered here`) after the operative sentence already fixed
  the position.

Keep one qualifier that defines a genuine boundary: a source limit, a reserved issue, a non-admission, a
redaction condition, a disputed status, a user-authority gap. Cut the repetition around it.

| Anxious over-qualification (cut to one clean limit) | Necessary boundary (keep) |
|---|---|
| `X does not assert he was 'ordered' or 'forced'; the records are silent as to motive; X asserts none and puts it no higher than ...` | `X relies on the records only for what they independently establish.` |
| a redaction recital re-listing every field that stays legible | `the footer address will be redacted before service, subject to the verified forum process.` |
| `premature, and is neither admitted nor answered here` | `premature.` (the non-admission is already stated once elsewhere) |
| `the records cut both ways` | the limited-purpose sentence that already states what the records are and are not relied on for |

A point made once, plainly, with its single necessary limit, is stronger than the same point hedged three
ways. Distinguish this from honest negatives (non-service, non-admission, no finding, reserved issue, source
limit): those mark boundaries and stay. Defensive over-qualification only manages how the reader might react,
so it goes.

## Persuasive Strength

The companion to Defensive Over-Qualification: cutting the hedge is only half the job; the other half is putting
the point with confidence. Persuasive force comes from structure, precision and located candour, not from
intensifiers. Overstatement (`overwhelmingly`, `plainly`, `incontrovertibly`, `beyond doubt`) is a credibility
cost, not a gain, and the cost is measured: frequent intensifiers correlate with losing appeals, and emotional
language with losing merits votes (Long & Christensen 2008; Black et al 2016 - cites in
`argument-structure-and-paragraphing.md`, Sources). Claim the conclusion cleanly and let the evidence chain
carry it.

- **Assert the proposition, pin it to a source, drop the intensifier.** "The
  notice was received at 4:00 pm ([SOURCE PINPOINT]). The response period had
  already ended."
  Not "it is respectfully submitted that, arguably, the order may not have been served …", and not "the
  evidence overwhelmingly proves beyond doubt …".
- **Argumentative point-headings, not topic labels.** "The reasons disclose no finding on the agreed date"
  beats "The reasons".
- **Subordinate the opponent's point; keep your answer in the main clause.**
  "Although the report states the conclusion, its appendix records the contrary
  result; the conclusion does not follow."
- **One located concession beats a fog of caveats.** Make the assertion cleanly; put the single necessary
  qualification in the next sentence, not stacked onto the assertion.
- **Confront the obvious weakness and meet it**: volunteering and distinguishing an adverse point is stronger
  than side-stepping it, which reads as having no answer (see `argument-structure-and-paragraphing.md`,
  Adverse Authority And Candour).
- **Use the contention register at threshold/interlocutory stage** ("the applicant contends"; "the proper
  inference is"): strong without purporting to have proved a contested fact not yet tested.
- **Specificity is the confidence**: every contention carries a paragraph/exhibit/page so the bench can verify.
- **Mark arguments cumulative or alternative expressly**, and be proportionate in length.
- **Calibrate, never flatten.** Uniform confidence across strong and weak points reads as machine tone and
  wastes the advocate's most important signal. Full positive form on the strong points; an honest, located
  concession on the weak one.

This does not licence overstatement: keep honest negatives, source limits, disputed-status wording, reserved
issues and user-authority gaps. Confident ≠ overclaiming; the leave/threshold test is "reasonably arguable",
and a contested fact stays a contention.

## Register Discipline (Leave And Interlocutory Stages)

Pick the register the stage requires and hold it for the whole document; do not flip mid-paragraph between
"reasonably arguable" and "is established". Oscillation reads as either overclaim (asserting merits the stage
cannot decide) or anxiety (re-hedging a point already put), and it hands the other side a framing objection.

- Leave/threshold documents argue that grounds are `reasonably arguable` or that a question `warrants leave`;
  they do not declare contested facts proved. State the contention with full force inside that register: "it is
  reasonably arguable the party had no opportunity to answer the report" can
  still be developed with every pinpoint and consequence.
- A merits or final submission may assert `is established`, `the record shows`, `the only available inference`,
  where the record carries it.
- The two registers may coexist in one document only where the document genuinely does two jobs (a leave
  application with a fallback merits section); mark the boundary structurally with a heading, not sentence by
  sentence.
- Uncontested procedural facts stay plain fact register at every stage: `the decision was delivered on [date]`.

## Condense Integrity

Follow the hub's Condense integrity (deterministic token check, then an
independent qualitative pass; never patch a gap from memory). Legal-specific
token set: figures, dates, amounts, paragraph/page/line pinpoints, exhibit
labels, authorities and defined terms. Legal-specific qualitative question:
is any ground, particular, qualifier or honest negative now weaker, unowned
or unlocatable? Relocation risk is acute here: a premise moved too far from
the contention that uses it, or a numbered particular de-listed into prose,
can cost identifiability. Re-read the argument that relied on the moved
material and confirm it still lands with a pinpoint to the new home.

## Wrong-Home Repair

When a sentence is doing the wrong job, move it before rewriting it:

- affidavit argument goes to submissions;
- submission-level factual detail goes to an affidavit, chronology or exhibit note;
- reasons for an order go to submissions, not the order;
- relief buried in affidavit evidence goes to proposed orders;
- correspondence history goes to an attached outline or chronology if it is not needed in the email body;
- internal verification, manifest, render or audit language stays internal and is translated to the actual
  source or legal act in filing-facing prose.

Wrong-home material usually gets worse when it is polished. Relocate it first.

## Document-Specific Locks

Lock legally functional material before cutting:

- correspondence: protective labels, offer terms, non-admission or non-waiver wording, rights reservations,
  response deadlines and attachment/service statements;
- affidavit: facts within the deponent's direct knowledge, including observations, receipt, conversations,
  state of mind and actions. The sworn paragraph can be the evidence; lack of an external document goes to
  corroboration and weight, not automatic deletion;
- proposed orders: classify each item as an order, undertaking, notation/recital or reason. Orders need an
  actor, act, object and deadline or trigger. Missing enforceability details are flagged, not invented.

## Sentence Repair

The hub's condense-pass Sentence repair table covers the general wordy
forms (`in order to`, `the fact that`, `is able to`, and similar). Legal-only
additions:

| Wordy form | Repair |
|---|---|
| `for the purpose of` | `for` or the specific purpose |
| `in circumstances where` | `where`, `when` or the actual condition |
| `with respect to` | `about`, `for`, `on` or the precise legal relation |
| `it is submitted that` | state the submission directly, unless the forum style calls for it |
| `respectfully requests` | `asks` or `seeks`, unless formality is needed |

Release buried verbs (nominalisations): `make a determination` becomes `determine`; `give consideration to`
becomes `consider`; `reach a conclusion` becomes `conclude`; `is applicable to` becomes `applies to`; `conduct
an investigation into` becomes `investigate`. Heuristic: scan for `make`, `give`, `reach`, `conduct` or
`provide` followed by an abstract `-tion`/`-ment`/`-ance` noun, and restore the verb.

Collapse ceremonial doublets to the single operative word: `null and void` becomes `void`; `each and every`
becomes `each`; `any and all` becomes `any`; `full and complete` becomes `complete`; `cease and desist` becomes
the actual demand. Keep a pair only where the two words genuinely carry distinct legal content or the phrase is
a quoted, statutory or form-field term.

Collapse modal hedge stacks to one accurate qualifier: `may arguably, in some circumstances, be` becomes `is
arguably`; `could potentially` becomes `may`. Better again, replace the vague hedge with the precise legal
standard: `could perhaps be unreasonable` becomes `was not reasonably open on the evidence`. One well-placed
qualifier reads as care; a stack reads as anxiety (see Defensive Over-Qualification).

Preserve formal language where it is a rule phrase, form field, statutory expression, defined term, quoted text
or forum convention.

## Final Self-Audit

Before returning a draft, name the single concrete remaining defect, if any:

- overclaim;
- missing source;
- wrong document home;
- unsafe disclosure;
- machine rhythm;
- legal noun stack;
- false transition;
- unsupported legal conclusion;
- broad fairness closer;
- lost legal negative or source boundary.

If no concrete defect can be named, stop. Do not keep rewriting to satisfy an AI detector or a vague feeling
that the text should sound more human. Fix defects, not style anxiety.
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 implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall