policy-diff

Maps regulatory change requirements onto indexed UK policy library entries with gap classifications.

9|Updated May 18, 2026
One-click install
npx skills add https://github.com/uk-agents/uk-legal-plugins --skill policy-diff-uk-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: policy-diff
Source: https://github.com/uk-agents/uk-legal-plugins/tree/main/regulatory-legal-uk/skills/policy-diff
Command: npx skills add https://github.com/uk-agents/uk-legal-plugins --skill policy-diff-uk-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify exactly which pieces of your UK regulatory policy library are affected by a specific regulatory change, and what needs updating to stay compliant.

Core Features & Use Cases

  • Requirement-level extraction: Breaks the regulatory change into discrete, actionable requirements with regulator and in-force timing.
  • Indexed policy matching: Maps each requirement to the closest policy from the library (direct, indirect, or no match).
  • Diff-driven gap analysis: Produces per-requirement gaps (none, partial, full) and flags new-policy needs when no coverage exists.
  • Safety and provenance guardrails: Enforces rule-status verification prompts when the instrument’s in-force position is uncertain and requires clear source attribution for citations.
  • Special branch handling: Uses a pre-positioning approach for consultations/draft SIs rather than asserting binding “no gap” outcomes prematurely.

Quick Start

Use the policy-diff skill to diff the latest UK regulatory change you care about by running it with the regulation name, SI reference, or a pasted regulatory summary.

Frequently Asked Questions about policy-diff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a regulatory change gap analysis against an existing UK policy library?

Regulatory change gap analysis extracts discrete new or modified requirements from a rule change, mapping each to indexed policy entries to classify coverage as none, partial, or full. This identifies exactly which existing policies need updates to maintain compliance.

What is compliance mapping for UK statutory instruments and how does it work?

Compliance mapping for UK statutory instruments breaks down regulatory changes into actionable requirements, verifies the instrument's in-force status, and maps each requirement to the closest existing policy using OSCOLA-formatted citations with clear source attribution.

How do I check which policies are impacted by a specific FCA handbook update?

To check policy impact from an FCA handbook update, extract the modified requirements and match them against your indexed policy library. The process flags direct, indirect, or no matches to highlight specific policy gaps requiring remediation.

Can I use policy gap analysis for draft SIs or consultations that are not yet in force?

Yes, policy gap analysis handles draft SIs and consultations using a pre-positioning approach rather than asserting binding outcomes. It enforces rule-status verification prompts to prevent prematurely concluding no gap exists when the instrument's in-force position is uncertain.

What is the best way to identify new policy needs when no existing coverage exists for a regulatory change?

The best way to identify new policy needs is to extract discrete requirements from the regulatory change and map them to your indexed library. When no coverage exists, the analysis explicitly flags a new-policy need rather than classifying it as a partial gap.

Why does regulatory change mapping require rule-status checks before classifying policy gaps?

Regulatory change mapping requires rule-status checks because statutory instruments may have uncertain in-force positions. Verifying status prevents inaccurate gap classifications and ensures compliance mapping reflects the actual binding legal timing of the requirements.