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-correspondence-style.md

View on GitHub
# Legal Correspondence Style

Use this reference for emails and letters to registries, the other party, solicitors, service contacts and internal legal-support readers. Use the forum skill for filing method, service rules, deadlines and form requirements.

## Main Rule

Draft correspondence as if it may later be annexed, exhibited or read by a court or tribunal. That does not mean stiff language. It means accurate, courteous, short and source-aware language.

## Email Shape

Use this default order unless the forum or user gives a better structure:

1. Subject line: `[matter/file] - [request or action] - [date/deadline]`.
2. Salutation matched to the recipient.
3. First paragraph: why the email is being sent and what is requested or attached.
4. Necessary context only: one to three short paragraphs, source anchored where facts matter.
5. Attachments or filed material: list only what is attached or linked.
6. Next step: deadline, response requested, or practical action.
7. Sign-off matched to the salutation.

## Subject Lines

Prefer short, searchable subjects:

- `[FILE NUMBER] - service material - filed [DATE]`
- `[FILE NUMBER] - request for remote appearance - [DATE]`
- `[FILE NUMBER] - supplementary affidavit - response requested by [TIME] [DATE]`

Avoid vague subjects such as `Important update`, `Documents`, `Further correspondence` or `Please see attached`.

## Salutations And Sign-Offs

- Registry or court staff: `Dear Registrar` or `Dear [title/name]`; sign off `Yours faithfully` or `Kind regards` depending on formality.
- Known solicitor: `Dear [name]` or `Dear Ms/Mr/Mx [surname]`; sign off `Yours sincerely` or `Kind regards`.
- Other party or self-represented person: use a neutral `Dear [name]`; keep tone courteous and factual.
- Internal legal-support note or draft email for user review: use the recipient's likely real-world salutation, not agent process language.

Use `Hi` only for informal internal or familiar professional correspondence where the existing thread supports that tone. Do not use archaic or theatrical openings.

## Tone

- Be courteous, firm and practical.
- Write like a careful person making a record, not like a template.
- Answer the issue, not the emotion in the previous email.
- Do not threaten, bait, editorialise or sound wounded.
- Do not over-apologise or over-explain.
- Do not make legal threats, concessions, undertakings, settlement offers, service admissions or rights-reservation statements unless the user instruction and forum context support them.
- If a reply is likely to escalate conflict, draft a short holding response or suggest a non-email step for user decision.

## Concision Rules

- Put the request, answer or attachment list before background.
- Use one topic per paragraph.
- Keep most emails under five short paragraphs unless they are formal letters of advice, registry requests or service cover letters.
- Remove repeated procedural history. Use one dated sentence and a source anchor where needed.
- Replace legalese with ordinary words unless the legal term is needed for accuracy.
- Preserve exact dates, file numbers, document labels and deadlines.
- Use one practical request, answer or next step per paragraph.
- Do not add pleasantries, apology, outrage, empathy, settlement framing, undertakings, concessions, service admissions or rights reservations as style devices.
- If a sentence would sound strange when read aloud to a court, make it plainer without changing its legal effect.
- Match the forum and document register, not a person's catchphrases from earlier letters or emails.

## Common Email Templates

### Registry Filing Or Service Cover

```text
Dear Registrar

I attach [document names] for filing in [matter number].

The documents are:

1. [document]
2. [document]

[One sentence on urgency, listing date or requested direction, if needed.]

Please confirm filing or advise if any further step is required.

Yours faithfully
```

### Other Party Service Cover

```text
Dear [name]

I attach the following documents filed or to be relied on in [matter number]:

1. [document]
2. [document]

Please confirm receipt by [time/date].

Kind regards
```

### Short Substantive Response

```text
Dear [name]

I do not agree to [request], for these reasons.

First, [short reason with source or date].
Second, [short reason with source or date].

The practical position is [next step or deadline].

Kind regards
```

## Scrub Before Sending

- Clear subject line.
- Correct recipient, `Cc`, attachments and protected-address handling.
- No protected address or unsafe contact detail.
- No unsupported accusation or exaggerated legal conclusion.
- No internal agent language, drafting notes or unresolved placeholders.
- No generic AI polish: `I trust this email finds you well`, `it is important to note`, `for the avoidance of doubt`, `we reserve all rights` unless genuinely needed and instructed.
- No bulky attachment list unless each item is necessary.
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