policy-redraft

Generates marked-up policy redraft proposals that close regulatory compliance gaps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a regulatory gap analysis identifies that an internal policy no longer matches a current rule, someone still has to draft the fix. This Skill produces a marked-up redraft of the affected policy section as a reviewable proposal, without ever touching the approved source document or prematurely closing the gap in the tracker. ## Core Features & Use Cases - Marked-up redrafts with rationale: Produces redlined policy sections (struck and inserted text) where every change carries an inline comment citing the rule, the citation, and the gap being closed. - Rule currency verification: Checks whether the underlying regulation is still in force (delays, stays, injunctions, rescissions) and emits a prominent warning banner when status cannot be verified. - Strict proposal guardrails: Writes output only to a clearly dated draft file like [policy-name]-proposed-redraft-[YYYY-MM-DD].md, never edits source policies, and never closes gaps in the tracker. - Use Case: After running a gap analysis that flags your data retention policy as conflicting with a new 14-day regulatory cap, invoke this Skill with the gap ID to receive a redraft memo showing the smallest possible edit, a change summary table, and a pre-application checklist for the policy owner. ## Quick Start Ask the assistant to redraft the policy section for a specific gap by saying something like: redraft the data retention policy to close gap GAP-014 from the tracker.

Frequently Asked Questions about policy-redraft

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

FAQPage Schema
How do I redraft a policy to close a regulatory compliance gap?

Provide the gap ID from the gap tracker (or describe the gap), the current approved policy text, and the rule text. The Skill produces a marked-up redraft of only the affected sections with inline comments explaining each change, written to a dated proposal file.

What inputs does a policy redraft workflow require?

Three inputs are mandatory: the gap (tracker ID, description, or diff output), the current policy text (file path or pasted), and the rule text (from a diff, fetched regulation, or user paste). If any is missing, the Skill asks rather than inferring.

Can the redraft be applied directly to the approved policy document?

No. The output is a proposal written to a new file named with 'proposed-redraft' and the date. Applying the change is the policy owner's action after review and approval; the Skill explicitly declines requests to edit source policies.

Does the redraft close the gap in the compliance tracker?

No. The gap closes only when the redraft is applied and approved by the policy owner. The Skill never modifies tracker state and will decline requests to mark a gap closed after drafting.

What happens if the regulation's status cannot be verified?

The Skill emits a 'RULE STATUS UNVERIFIED' banner above the work product and tags every effective date as unverified. It warns that final rules are frequently stayed, enjoined, delayed, or rescinded and directs confirmation via the Federal Register docket or outside counsel.

What are the limitations of automated policy redrafting?

It handles one gap, one policy, and one memo at a time — no multi-policy fan-out. It makes only the smallest edit needed for the flagged gap, does not restyle the policy, and does not silently fix unrelated issues it notices, flagging them for follow-up instead.