policy-diff

Diffs regulatory changes against indexed policy libraries to identify gaps and required updates per requirement.

Updated May 15, 2026
One-click install
npx skills add https://github.com/az9713/claude-for-legal-tutorial --skill policy-diff-az9713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: policy-diff
Source: https://github.com/az9713/claude-for-legal-tutorial/tree/main/regulatory-legal/skills/policy-diff
Command: npx skills add https://github.com/az9713/claude-for-legal-tutorial --skill policy-diff-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies which internal policies need updates when a regulation changes, by extracting new or changed requirements and comparing them against your indexed policy library to produce gap analysis.

Core Features & Use Cases

  • Requirement extraction and validation: Breaks a regulatory input into discrete new or changed requirements and flags when rule status cannot be confirmed.
  • Policy mapping and diffing: Matches each requirement to the closest indexed policy (direct, indirect, or none) and generates per-requirement diffs showing what the policy covers versus what it misses.
  • Special handling for non-final regulatory inputs: Uses a pre-positioning analysis for ANPR/RFI inputs instead of full gap-closure diffs, and compresses outcomes when the identified target policy is already sufficient.

Quick Start

Use the policy-diff skill to diff the regulation against our indexed policy library by running: policy-diff with the input "diff this reg against our policies" plus the regulation name or the reg text/summary.

Frequently Asked Questions about policy-diff

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

FAQPage Schema
How do I identify which internal policies need updates after a regulatory change?

Policy gap analysis compares newly extracted regulatory requirements against your indexed internal policies to identify direct matches, indirect matches, or missing coverage. It produces per-requirement gap outputs showing exactly what existing policies cover versus where compliance gaps remain.

Can I perform a policy gap analysis on non-final regulatory inputs like an ANPR or RFI?

Yes, you can analyze non-final regulatory inputs such as an ANPR or RFI through a pre-positioning analysis rather than a full gap-closure diff. This approach evaluates preliminary regulatory changes to prepare your policies without finalizing compliance updates prematurely.

How do I map new regulatory requirements to existing corporate policies?

Mapping new regulatory requirements to existing corporate policies involves matching each extracted requirement to the closest indexed policy and generating a diff. It categorizes matches as direct, indirect, or none, and highlights specific areas where the policy misses compliance obligations.

What happens if the rule status of a regulatory requirement cannot be confirmed during a diff?

When rule status cannot be confirmed during a regulatory diff, the analysis flags the requirement and enforces scope limitation banners and non-final-input handling. This ensures unverified regulatory changes are not treated as final compliance obligations for policy updates.

Does policy gap analysis provide citations and ownership routing for compliance gaps?

Yes, policy gap analysis provides citations and policy ownership routing for identified compliance gaps. The output details exactly which policies require updates, includes citations to the regulatory text, and routes the update responsibility to the appropriate policy owners.