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/forum-and-document-recipes.md
View on GitHub# Forum Adapter And Document Functions
Use this reference to adapt general Australian legal-writing doctrine to the
actual forum, procedural stage and document. It supplies no current law,
procedure or form rule. A project or jurisdiction skill may add stricter
instructions, but the current official source and the supplied form or template
control.
## Build The Forum Adapter First
Before drafting, record the minimum verified adapter:
- jurisdiction, forum, proceeding and procedural stage;
- document name, function, intended reader and relief or action it supports;
- current party, decision-maker, instrument and document labels;
- mandatory form or template, fields, annexures and signature requirements;
- current length, layout, citation, filing, service and deadline rules;
- source hierarchy and any evidence-use restriction;
- confidentiality, suppression, safety, redaction and contact-detail rules;
- the official URL or instrument, version or effective date, and date checked;
- every unresolved point that needs human or qualified legal review.
Do not infer one forum's terminology or procedure from another. Do not treat a
convenient house style as cross-forum compliance. If the adapter is incomplete,
draft only a clearly marked internal working version and stop before
filing-facing completion.
## Precedence
Apply instructions in this order:
1. governing law, orders and current official forum material;
2. the supplied official form, template or filing specification;
3. project and matter instructions, including source and safety boundaries;
4. the verified forum adapter;
5. this skill's neutral drafting defaults.
Never silently repair a conflict. Preserve the source wording, identify the
conflict and escalate it.
## Document Function Matrix
| Document | Primary function | Keep in it | Move out of it |
|---|---|---|---|
| Form-bound application or response | Invoke a process and state the requested disposition | Exact fields, verified labels, concise grounds, required declarations | Narrative beyond the field's function, unsupported legal conclusions |
| Affidavit or witness statement | Give admissible or potentially admissible evidence | First-person facts, source-linked documents, necessary foundation | Argument, legal characterisation and reasons for relief |
| Submissions or outline | Apply verified law to the record and relief | Issues, rules, argument, materiality, answer and relief | New evidence and unsupported factual assertion |
| Proposed orders or minute | State commands sought | Actor, act, object, deadline or trigger, and any necessary condition | Reasons, evidence recitals and advocacy |
| Chronology or schedule | Navigate dates, events, issues or calculations | Stable labels, exact figures and source pinpoints | Free-standing argument not made in submissions |
| Correspondence | Communicate a practical legal step | Request, position, deadline, attachments and next step | Unnecessary pleading, threats or concessions |
| Annexure or exhibit index | Navigate source material | Exact labels, titles, dates, page ranges and source identity | Analysis or a substitute for the source |
| Internal advice or case note | Analyse options and risk | Assumptions, uncertainty, competing readings and verification gaps | Material presented externally without review and authority |
| Statutory declaration | Declare a fact outside a proceeding under a declarations Act | Prescribed wording, first-person facts, identified attachments | Argument, opinion the declarant cannot give, uncertain facts |
| Deed or agreement | Create, vary or release obligations | Parties, defined terms, operative obligations, execution blocks | Advocacy, unverified recitals, obligations hidden in recitals |
| Letter of demand or pre-action letter | Require an act or payment and create a record | Identity, dated facts, legal basis, the act required, the deadline | Threats without instruction or basis, misstatement of legal effect |
| Tribunal application or contentions | Start or frame a merits review | The decision under review, the statutory criteria, the disposition sought | Judicial review grounds, court costs assumptions, ceremonial advocacy |
## Orders And Minutes
An order is an operative command, not a submission. For each proposed order,
verify:
- the forum can make it and the applicant has a proper procedural route;
- the wording identifies who must do what, to what, and by when or on what
trigger;
- it does not duplicate another order, a form field or an automatic procedural
consequence;
- it does not ask one forum to control another proceeding;
- any condition, undertaking, notation or recital is correctly classified;
- it matches the relief and evidence in the other documents; and
- the rendered title, numbering, defined terms and cross-references agree.
Do not invent a power, default procedure, service method or costs consequence.
Where the result depends on current rules or directions, cite the verified
source in the submissions or internal verification record. Put reasons in
submissions, not in the operative order.
## Affidavits And Witness Statements
For a statutory declaration, or for the choice between a declaration, an
affidavit and a witness statement, load `statutory-declarations.md`. For a
tribunal rather than a court, load `tribunals-and-merits-review.md`. For a
deed, agreement or other transactional instrument, load
`deeds-and-agreements.md`.
- Use the source's required person, oath or affirmation language and template.
- State facts the deponent or witness can properly give, with dates and document
anchors where available.
- Distinguish personal knowledge, information and belief, recollection,
inference and quoted material as the governing law and form require.
- Describe lived experience in lay terms unless admissible expert or medical
evidence supports a diagnosis.
- Do not convert disputed conduct, another document's allegation or another
proceeding's submission into a fact.
- Annex or exhibit only what is needed and permitted. Keep enough context for a
fair reading and verify authentication, labelling and privacy requirements.
- Check every paragraph, page and cross-reference against the current form,
rules and rendered document. This skill supplies no universal page cap or
numbering scheme.
## Submissions And Written Advocacy
For each issue:
1. State the answer or proposition.
2. Identify the verified rule, authority, order or threshold.
3. Apply source-anchored facts at their true evidentiary status.
4. State the consequence for the relief sought.
Use the stage's correct register. Threshold or interlocutory writing must not
present contested merits as findings. A final-stage assertion still needs the
record and legal test to carry it.
## Cross-Proceeding Material
- Identify which forum, order and document each proposition comes from.
- Use another proceeding's material only for a purpose the receiving forum may
consider and the source can prove.
- Do not ask one forum to grant relief reserved to another or to re-decide a
subsisting order indirectly.
- Treat pleadings, submissions and allegations from another proceeding as
statements of position, not proof of their underlying facts.
- Verify any issue of jurisdiction, finality, issue preclusion, abuse of process
or appellate effect from current primary authority and obtain human or
qualified review before asserting it.
## Speaking Outlines And Correspondence
A speaking outline should be a navigation layer over filed material: issue,
answer, exact record pinpoints and the expected question. Do not create a second
argument or add an unfiled point without authority and procedural verification.
For correspondence, load `legal-correspondence-style.md`, and
`demands-and-pre-action-correspondence.md` for a demand, a pre-action letter or
a settlement offer. Match the recipient
and existing thread, state the practical request and deadline early, list only
the material actually attached or linked, and preserve any authorised
non-admission, privilege, settlement or rights language exactly.
## Completion Gate
The document is not filing-ready merely because the prose is clean. Confirm the
forum adapter against current official sources, validate source and document
function boundaries, render the actual output, obtain required human or
qualified review, and keep filing, service, signing and sending as separately
authorised actions.
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 |