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/verification-and-escalation.md

View on GitHub
# Verification And Escalation

Apply the owning project's authority and source gates. This reference is a
portable verification protocol, not a substitute for current Australian law,
forum procedure or qualified legal review.

## Source Hierarchy

Use the highest-authority current source available for the proposition:

1. legislation and delegated instruments on the responsible official
   legislation service;
2. judgments, orders and reasons from an authorised court or tribunal source;
3. current rules, practice directions, forms, filing guidance and notices from
   the relevant official forum;
4. sealed, issued, filed, served or otherwise authenticated proceeding records;
5. original evidence permitted by the project's source protocol; and
6. secondary commentary for orientation only, unless the task expressly calls
   for it and its status is clear.

An index, search result, summary, OCR layer, transcript, render or working note may
locate a source. It does not replace that source. Check commencement,
amendment, transitional provisions, supersession and the proposition's relevant
date before calling a source current.

## Verification Record

For every rule, form, procedural statement or important fact, record:

- the proposition supported;
- source title and stable URL or repository path;
- issuing body and jurisdiction;
- version, effective date or relevant date range;
- exact section, rule, paragraph, page, line, field or timestamp;
- date checked and whether the source itself was opened; and
- any conflict, qualification or unresolved interpretation.

Do not report `filed`, `served`, `lodged`, `accepted`, `sealed`, `signed`,
`witnessed` or `sent` without evidence for that distinct state.

## Escalate Rather Than Infer

Stop at an internal, clearly qualified draft when:

- the forum, procedural stage, form or source hierarchy is uncertain;
- official sources conflict or the relevant version cannot be established;
- the requested wording would change a contention into a finding;
- confidentiality, privilege, suppression, safety or redaction is unresolved;
- an authority or quotation cannot be pinpoint-verified;
- the task requires legal judgement beyond the supplied instructions; or
- a signature, certification, undertaking, concession, filing, service or
  external communication lacks current user authority.

Record the competing readings and practical consequence in the project's
canonical control or status document. Do not hide the gap in polished prose.

## External-Action Gate

Drafting and verification do not authorise filing, lodging, service, upload,
signature, witnessing, certification, disclosure or communication. Treat each
external act and recipient as a separate user-authorised step, then retain the
evidence that proves what occurred.
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