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/family-violence-and-redaction.md

View on GitHub
# Safety-Sensitive Material And Redaction

Use this reference for family-violence, personal-safety and other sensitive
material. It supplies drafting and source-boundary controls, not substantive
law or a universal redaction procedure. Load the relevant jurisdiction or
matter skill and verify current official requirements.

## Name The Source At Its True Status

Use the title, issuer, date and status shown by the source, for example:

- `[PROTECTIVE INSTRUMENT] made/issued on [DATE]`;
- `the application or allegation recorded in [SOURCE]`;
- `the affidavit affirmed on [DATE]`;
- `the finding at [PINPOINT]`;
- `contemporaneous safety context`; or
- `alleged family violence`.

An application, allegation, police-issued instrument, interim measure, final
order and reasons containing a finding are different sources. Do not collapse
them. A protective instrument may prove that it exists and what it says; it
does not by itself prove every underlying allegation. Use finding language only
where an authorised source contains the finding and the proposition is relevant
for the present purpose.

Do not label a person a perpetrator, diagnose behaviour, or assert coercive
control, abuse of process or criminal conduct unless the source, current law,
document function and authorised litigation position support that exact claim.

## Purpose And Proportionality

- State why the sensitive material matters in this document: participation,
  communication, service, urgency, risk, confidentiality, procedure, prejudice
  or another verified issue.
- Use the least sensitive material that proves the point. Prefer a targeted
  extract only when it remains fair and intelligible; otherwise use the minimum
  complete context the forum requires.
- Separate safety context from merits proof. Do not use a safety recital to
  obtain a character finding the present document does not need.
- Keep graphic, medical, reproductive-health, child and third-party detail out
  unless necessary, source-supported and authorised.

## Redaction And Confidentiality Gate

Before external use, identify and review:

- residential and service addresses;
- unsafe phone numbers, email addresses and location data;
- employer, school or routine information that can reveal location;
- account, card, identity and health identifiers;
- children's and third parties' identifying details;
- metadata, image backgrounds, headers, footers and attachment properties; and
- broad message histories where a targeted, contextual extract would suffice.

Never assume redaction, separate confidential filing, restricted access or
alternative service is permitted. Verify the current mechanism, what the other
party receives, what the decision-maker receives, and whether an unredacted
version is required. Redact the source and all derivative layers consistently,
then inspect the rendered document to ensure the information cannot be copied,
searched or recovered.

## Cross-Proceeding Consistency

Keep the safety objective and source status consistent across related
proceedings, but draft each request for the receiving forum. Do not transplant
another forum's terminology, powers, protective process, service rules or
orders. Record unresolved disclosure, service, confidentiality and protective
direction choices for human or qualified review.

## Hard Stops

Do not disclose protected contact details, waive a protection, publish
sensitive material, communicate with a prohibited recipient, or make a filing
or service decision without current authority. If the source status, intended
use or permitted redaction process is uncertain, stop at an internal draft and
state the gap.
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