policy-diff

Diff regulatory changes against an indexed policy library to identify compliance gaps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a regulation changes, legal teams must manually figure out which internal policies are affected and where the gaps are. This Skill automates that comparison, extracting discrete requirements from the regulatory change and mapping each one against your indexed policy library. ## Core Features & Use Cases - Requirement Extraction: Parses a regulatory change into a table of discrete, specific requirements with effective dates and citations, each tagged with its source. - Policy Mapping & Gap Analysis: Matches each requirement to indexed policies (direct hit, indirect, or no match) and produces per-requirement gap findings with specific change recommendations and policy owners. - Branch-Aware Output: Handles ANPR/RFI pre-positioning analysis, negative-finding summaries, and full gap diffs differently, with rule-status verification warnings and scope-limitation flags. - Use Case: A final rule from a regulator lands in your inbox. Run the diff to get a summary table of which policies need updates, which gaps are Partial or Full, and hand off tracked items to gap-surfacer with owners and deadlines. ## Quick Start Ask the assistant to diff the new regulation against your policy library by pasting the regulation text or naming the rule.

Frequently Asked Questions about policy-diff

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

FAQPage Schema
How do I check which policies a new regulation affects?

Run the policy diff with the regulation name or pasted text. It extracts each discrete requirement, maps them against your indexed policy library, and reports which policies are directly or indirectly affected, plus any requirements with no matching policy.

How to perform a regulatory gap analysis against internal policies?

Provide the regulatory change text and the skill extracts requirements into a table, reads each matched policy, and classifies each gap as None, Partial, or Full with a specific change needed and the policy owner from your library index.

What happens if my policy library is empty or not configured?

Every requirement is flagged as a no-policy-match gap by default, and the output notes that the library is empty. You can populate it via the cold-start-interview command or by editing the regulatory-legal CLAUDE.md config, then re-run the diff.

Does the diff verify that a regulation is actually in force?

Yes. Before diffing, it checks for red flags like passed compliance dates or contentious final rules and looks for stays, injunctions, or delays. If status cannot be verified, it emits a warning banner and tags all due dates as unverified.

What are the limitations of automated policy gap analysis?

It does not draft the policy updates or definitively interpret ambiguous regulatory text; ambiguous readings are flagged for counsel. AI-generated citations must be verified against primary sources like Westlaw or the issuing authority before relying on them.