agentleFS
SprintlawSprintlaw/legal-skills/skills/jurisdiction-adapt/SKILL.md

jurisdiction-adapt

Skill0 starsChanged 33 days agoMITView on GitHub

Adapt a contract, policy or precedent from one country's law to another's (for example Australian to New Zealand, UK or US, or between US states) without leaving remnants, losing mandatory content or shifting the commercial balance. Builds a concept and statute map, plans every clause (keep, change, add, delete), edits the original file in place rather than rewriting, adds the target's mandatory content, scans for remnants, and runs a hostile target-jurisdiction review until PASS. Use for "localise", "adapt for New Zealand", "Americanise", "make this work under UK law", "convert this precedent", or whenever a document from one jurisdiction will be used in another.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the commercial position.

    line 19
  2. Very specific:

    Every target-law reference is verified from the official source (cite-check) or tagged [unverified].

    line 20
  3. Distinctive:

    Start from references/concept-map.md, then confirm each row against the target pack's area files.

    line 34
  4. Distinctive:

    Before editing, write a plan with one row per clause:

    line 38
  5. Very specific:

    Run adversarial-review with the reviewer as a senior lawyer in the target jurisdiction who did not do the adaptation.

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Jurisdiction adapt

Adapting a document across borders looks like find-and-replace. It is not. The dangerous errors are the ones that read naturally: a consumer-law carve-out that names the wrong Act, an execution block that would not create a valid deed, a contracting-out clause that is lawful in one country and an offence in the other, an employment clause that the new country's statute overrides. In Sprintlaw's adaptation of 26 Australian precedents to New Zealand law, careful drafters still left errors in almost every document until a hostile local reviewer went through them.

Non-negotiables

  • Load both jurisdiction packs, and read the target pack's traps.md and conventions.md in full before touching the document.
  • Edit the original file. Do not retype or rebuild it: rebuilding loses formatting, numbering and the drafting choices you did not notice.
  • Keep the commercial position. Adaptation changes the law, not who the document favours.
  • Every target-law reference is verified from the official source (cite-check) or tagged [unverified].
  • Where the target has no equivalent concept, say so and redesign the clause. Never force a source concept into the target with a new label.

Step 1. Inputs

Source document (ideally .docx), source and target jurisdictions (and state for AU and US), document type, whose side it favours, and how it will be used (one client, or a precedent for many).

Step 2. Concept and statute map

Build a table for this document:

Source concept or statuteTarget equivalentSame effect?Notes

Start from references/concept-map.md, then confirm each row against the target pack's area files. Mark rows where the target works differently ("no statutory equivalent", "narrower", "different threshold", "different mechanism") because those clauses need redesign, not relabelling.

Step 3. Clause plan

Before editing, write a plan with one row per clause:

| Clause | Action (keep / change / add / delete) | Why | Target authority |

Include additions the target requires (mandatory content, local market practice) and deletions of source-only mechanics. Check the plan against the target pack's completeness expectations and the draft-contract checklist for the document type.

Step 4. Edit

Apply the plan to the original file with format-preserving edits (redline for tracked changes, or direct editing where a clean adapted precedent is wanted). Then:

  • Defined terms, cross-references and schedules updated for every change.
  • Parties block, entity types and identifiers in target form.
  • Tax clause (GST, VAT, sales tax) in target form.
  • Governing law, courts and dispute-resolution bodies in target form.
  • Execution blocks valid for the target, including deed formalities and electronic signing.
  • Currency, spelling and date format for the target.
  • Drafting notes rewritten for the target or removed.

Step 5. Remnant scan

Run doc-audit with --jurisdiction <target>. Then search the text for the source's remnant list in the target pack's traps.md, for example: source statute names, regulators, courts, entity suffixes, identifiers, states and territories, tax words, currency symbols, and source spelling. Read the whole document once more for subtle remnants (concepts with the right name but the wrong mechanism).

Step 6. Hostile review

Run adversarial-review with the reviewer as a senior lawyer in the target jurisdiction who did not do the adaptation. Fix and re-review until PASS (three rounds maximum). For a set of documents, finish with the cross-document sweep for every bad string found.

Reply

The adapted document (clean and tracked versions where possible); a change log by clause; the citation table; the concepts that had no equivalent and how they were handled; remaining [judgment] calls for a local lawyer.

Direction notes

  • Into New Zealand: consumer and fair trading contracting-out rules differ sharply from Australia's; employment documents need mandatory content and trial-period mechanics specific to NZ; deeds and company execution follow NZ statutes; no states.
  • Into the UK: England and Wales by default; flag Scotland. Consumer cancellation and unfair terms regimes differ from Australia's; data protection is UK GDPR plus the Data Protection Act; VAT, Companies House, and Companies Act execution.
  • Into the US: choose the state; never default silently to Delaware (use a [State] placeholder and a drafting note if unknown). Americanise spelling and drafting conventions; make disclaimers and caps conspicuous; check state rules on non-competes, arbitration, jury waivers, automatic renewal and privacy.
  • Into Australia: Commonwealth and state layers; consumer guarantees cannot be excluded for consumers; unfair contract terms rules cover standard form consumer and small business contracts, with penalties; state-specific leases, security of payment and limitation periods.

These notes orient; the target pack decides.

Limits

  • Some documents do not adapt well (employment agreements, leases, regulated-industry terms). Rebuilding from a target-jurisdiction precedent can be safer; say so when it is.
  • A locally qualified lawyer should read any adapted precedent before it is used widely.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.