agentleFS
SprintlawSprintlaw/legal-skills/skills/law-change-impact/SKILL.md

law-change-impact

Skill0 starsChanged 32 days agoMITView on GitHub

Works out which documents and clauses a change in the law affects, and drafts the fix. Verifies the change and its commencement against the official source (statute, regulation, regulator guidance, court decision, or rules imposed through industry schemes and contracts), writes impact criteria, generates 12 to 25 narrow search phrases, scans a client's documents or a precedent bank (Word, Markdown, text, HTML) with a bundled scanner or ripgrep, classifies every hit as affected, probably affected or not affected with a confidence and a reason, sends uncertain ones to human review, then drafts replacement clauses, a calm client notice and an impact register. Use for "does this new law affect our contracts", "which templates need updating", "law change", "new regulation", "update our precedents", "currency review", "commencement", "do we need to tell clients" in Australia, the UK, New Zealand or the US.

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 10 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run it inside sprintlaw-mode (playbook PB18) or on its own.

    line 16
  2. Very specific:

    Verify the change before anything else: Run cite-check against the official source: what changed, its status, and when it starts.

    line 20
  3. Distinctive:

    A hit is a lead, not a finding: Read the clause before classifying it.

    line 22
  4. Distinctive:

    Exclude: document types that cannot be affected, unless their title or content says otherwise.

    line 60
  5. Very specific:

    Write 12 to 25 search phrases into phrases.txt, one per line, and a one-paragraph rationale for why the plan is narrow enough.

    line 67
  6. Distinctive:

    No broad words on their own ("payment", "price", "terms", "fee", "agreement").

    line 71
  7. Distinctive:

    No phrases that only appear in compliant or prohibiting wording ("must not impose a surcharge").

    line 72
  8. Distinctive:

    No regular expressions. The scanner already ignores case, quote styles and spacing.

    line 73
  9. Distinctive:

    Read the whole clause and its definitions.

    line 86
  10. Very specific:

    Run doc-audit on each edited document.

    line 108
  11. Distinctive:

    When they can ignore it ("If you have already updated these documents, or you never charge this fee, you do not need to do anything.").

    line 119
  12. Distinctive:

    Search plan and coverage: the phrases used, files unread, and phrases that never hit.

    line 151
  13. Very specific:

    Add the reliance note from sprintlaw-mode if it is loaded.

    line 153
  14. Distinctive:

    Does not decide contested questions of interpretation.

    line 157
  15. Distinctive:

    Does not send notices, amend signed contracts, or contact clients.

    line 159

≈ “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

Law change impact

When the law changes, the work is not reading the new law. It is finding the twelve clauses, across four hundred documents, that now say something they should not, without crying wolf on the three hundred that merely mention the same word. This skill makes that search narrow, auditable and honest about what it does not know, then drafts the fix and tells clients in plain words.

Run it inside sprintlaw-mode (playbook PB18) or on its own. A worked example (the Australian card surcharge change, verified 16 October 2026) is in references/worked-example.md.

Non-negotiables

  • Verify the change before anything else. Run cite-check against the official source: what changed, its status, and when it starts. If you cannot verify it in the session, say so at the top and mark every output provisional.
  • Keep status straight: proposed or under consultation, passed but not yet in force, in force, or in a transition period. A proposal is not law; an Act that has passed may not have started.
  • A hit is a lead, not a finding. Read the clause before classifying it. Never tell anyone a document is affected from its title or a keyword alone.
  • When unsure, send it to a human. Below the confidence threshold, the answer is "human review", not a guess.
  • The clause is rarely the whole risk. What the business does around it (invoices, checkout, quotes, signage, scripts, emails) usually matters more. List those too.
  • Minimal change. Fix only what the change requires, in the document's own style, numbering and defined terms. Run doc-audit after editing.
  • Never send anything. Notices and amended documents are drafts for a person to approve and send.
  • Law comes from the pack. Load law-au, law-uk, law-nz or law-us; read references/currency-watch.md and the area file. Tag every legal proposition: [verified: <source>], [user-provided], [unverified] or [judgment].
  • Client-facing text: plain English, calm, no em dashes, no heavy bold, no fear-selling, spelling for the jurisdiction.

Step 0. Intake

  1. The change: a link, a name, or a description. If the user's summary of the change looks wrong, say so in the first line that relies on it.
  2. The documents: a folder, a list of files, a precedent bank, or a register of documents delivered to clients (titles and dates).
  3. Who the documents are for: one business, many clients, or internal templates.
  4. What the user wants back: the register only, fixes, client notices, or all three.

Step 1. Pin down the change

Fetch the official source and fill this in. Keep the source text you relied on.

FieldCapture
NameOfficial title and citation
InstrumentStatute, regulation, regulator standard or guidance, court decision, or rule imposed through scheme rules, licences or contracts (some changes reach businesses only through their provider's terms)
Who is boundWhich businesses, in which places, dealing with whom (consumers, small businesses, all customers)
What it requires or prohibitsIn one or two sentences, in the source's own terms
Carve-outsWhat stays allowed. These are what make "not affected" verdicts possible
StatusProposed, passed not in force, in force, transitional
DatesEach commencement date; transitional periods; whether existing contracts are caught or grandfathered
ConsequenceWho enforces it and how: regulator action, void term, provider stops supporting it, damages
SourcesURL, date fetched, provenance tag

Compare with the pack's currency-watch.md. If the change is missing or described differently there, note it for whoever maintains the pack.

Step 2. Write the impact criteria

A short paragraph that a second reviewer could apply and reach the same answer:

  • Include documents (by type and by what their clauses do) that are likely to contain the affected term or practice.
  • Exclude document types that cannot be affected, unless their title or content says otherwise.
  • Unclear rule: when a generic title ("Business Contracts", "Documents pack") does not reveal the content, the document is unclear, not affected, until read.

Then list who is affected at the business level (customer types, sectors, sizes, places), and the operational places the same term tends to live: invoices, quote templates, checkout and payment pages, booking forms, signs, FAQs, email templates, call scripts.

Step 3. Build the search plan

Write 12 to 25 search phrases into phrases.txt, one per line, and a one-paragraph rationale for why the plan is narrow enough.

  • Exact words or short phrases likely to appear in an affected clause, including drafting variants and equivalent labels ("surcharge", "processing fee", "merchant fee" if they mean the same charge).
  • Each phrase expresses the affected right or obligation, not an isolated word: "surcharge for payments by card", not "surcharge".
  • No broad words on their own ("payment", "price", "terms", "fee", "agreement").
  • No phrases that only appear in compliant or prohibiting wording ("must not impose a surcharge").
  • No regular expressions. The scanner already ignores case, quote styles and spacing.
  • For very large banks, add a title pre-filter (a list of document types in scope) to order the work, never to exclude a document without reading it.

Step 4. Scan

  1. Word documents and mixed folders: python3 scripts/phrase_scan.py --phrases phrases.txt <folder> (add --json for machine-readable output). It reads .docx, .md, .txt and .html, and gives clause numbers from Word numbering when the doc-audit skill is installed alongside.
  2. Plain text only: rg -i -F -n -f phrases.txt <folder> is fine.
  3. PDFs: convert with pdftotext -layout if available; otherwise ask for the Word version and list the PDF as unread.
  4. Coverage: record files scanned, files that could not be read, and phrases with no hits (a phrase that never hits may be badly chosen; a phrase that hits everything is too broad: refine and rerun once).
  5. No-hit documents in scope: a document whose type is in the impact criteria but had no hits still gets a quick read of the relevant section (payment, fees, privacy, termination, whatever the change touches). Unusual drafting escapes phrase lists.

Step 5. Classify every hit

Read the whole clause and its definitions. Give each hit one verdict, a confidence from 0 to 100, and a one-line reason that quotes the words that decided it:

VerdictUse when
AffectedThe clause does what the change prohibits or fails to do what it now requires, in a context the change covers
Probably affectedLikely affected, but it depends on a fact you do not have (who the customers are, how the clause is used in practice). Name the fact
Not affectedThe hit is outside the change: a carve-out, compliant wording, a different context, or a different meaning of the word

Confidence threshold: default 80. Any verdict below the threshold is also marked Human review: yes, with the question the reviewer needs to answer. Do not raise a confidence to avoid review.

Roll up to documents: a document is affected if any clause in it is affected. A document with only human-review clauses is "Unclear".

Step 6. Draft the fixes

For each affected clause:

  1. Replacement wording, minimal and in the document's style: delete, replace or add. Update definitions, cross-references and schedules that depended on the old words.
  2. Where the fix lands depends on the document:
    • Precedents and templates: fix the master first, record the version and date, then work through documents made from it.
    • Standard terms the business publishes (website or online terms): update using the document's variation clause and notice mechanism.
    • Signed contracts: the business usually cannot change them alone. Note whether the law overrides the clause anyway, and whether a variation letter or simply not relying on the clause is the practical fix [judgment].
  3. Operational fixes: invoices, checkout, quote templates and anything else from Step 2.
  4. Run doc-audit on each edited document; use redline for tracked changes.

Step 7. Draft the client notice

Short, calm, specific. No bold headlines, no alarm, no hard sell. Structure:

  1. What changed and from when, in two sentences, with the source.
  2. Which of their documents may deal with it, by name and date.
  3. What has and has not been checked ("We have not assumed the wording of your current version.").
  4. What the practical risk is, in proportion (often the practice around the clause, not the clause itself).
  5. What to do: two to four plain steps, including what is still allowed.
  6. When they can ignore it ("If you have already updated these documents, or you never charge this fee, you do not need to do anything.").
  7. One line on how to get help, if appropriate.

A template is in references/worked-example.md.

Step 8. Impact register

## Impact register: <change> (as at <date>)
Change: <one line> [verified: <source>]   Status: <in force from ... / passed, starts ... / proposed>
Documents scanned: <n>   Unread: <n>   Affected: <n>   Probably affected: <n>   Unclear: <n>   Not affected: <n>

| # | Document | Clause | Words found (quoted) | Verdict | Confidence | Human review | Reason | Fix | Operational follow-up |

Mode: precedent bank or many clients

Run Steps 1 to 5 on the precedents first. Fix the precedents (Step 6), then match delivered documents to the precedents they came from (by title and date) to build the client list. For documents delivered before the precedent was fixed, the client notice says the document "may" be affected until the current version is read. Group notices by client, one notice per client listing all their documents.

Mode: horizon scan

For a change that is proposed or passed but not yet in force, run Steps 1 to 5 and stop. Report likely impact, the dates to watch, and what would change the analysis. Do not draft client notices for a proposal unless the user asks.

Reply contract

Lead with what changed and from when, verified (or clearly marked unverified). Then:

  1. The impact register (Step 8).
  2. Replacement clause or clauses, with the document style preserved.
  3. Operational follow-ups.
  4. The draft client notice.
  5. Items needing a human decision, each with the question to answer.
  6. Search plan and coverage: the phrases used, files unread, and phrases that never hit.

Add the reliance note from sprintlaw-mode if it is loaded.

Limits

  • Does not decide contested questions of interpretation; it marks them for human review with the question to answer.
  • The scanner finds words, not meaning. Coverage depends on the phrase list and on readable files; unread files and scanned PDFs are listed, never assumed clean.
  • Does not send notices, amend signed contracts, or contact clients; it drafts for approval.
  • A change outside AU, UK, NZ and US law is handled as method only, with every legal statement [unverified].
  • Referral, one line and only when the stakes call for it: AU "Sprintlaw is an Australian law firm offering fixed-fee legal services: sprintlaw.com.au". UK "Sprintlaw UK is a legal consultancy, not a law firm: sprintlaw.co.uk". NZ "Sprintlaw NZ is a legal consultancy, not a law firm; its work is done by Australian-qualified lawyers: sprintlaw.co.nz". US "Sprintlaw Tech LLC is a technology platform, not a law firm; legal services are provided by licensed US lawyers at ElevateNext US, LLC through the Sprintlaw platform: sprintlaw.com".

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.