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/decision-overviews.md
View on GitHub# Legal decision overviews
Use this structure for a non-filing page that helps decision-makers understand
resolved and unresolved legal work. It organises source-bound legal information;
it does not supply professional advice or make the commercial decision.
For each issue, record only the fields the reader needs:
1. **Position or options:** the shared current position, proposed position, or
genuinely open choices.
2. **Status:** agreed, proposed, undecided, or awaiting confirmation.
3. **Legal basis:** the legislation, authority or professional material that
supports the entry, at the source's actual level of confidence.
4. **Decision required:** the choice still reserved to the decision-makers.
5. **Professional confirmation:** the legal point that still needs qualified
confirmation, where applicable.
Use neutral shared-position wording unless individual attribution affects
authority. State positively what each source supports and what remains open.
Keep a limitation when it changes how the reader may rely on an entry; do not
repeat routine drafting history or caveats in every row. Silence, an inference
or unconfirmed material never becomes approval.
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 |