/policy-redraft

Load ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md → policy library index + practice profile.
Use the workflow below.
Gather inputs: the gap (from /regulatory-legal:gaps output or described directly), the current approved policy text, the rule text.
Verify the rule is current (per the policy-diff rule-status check). If you can't verify, emit the ⚠️ RULE STATUS UNVERIFIED banner.
Produce a marked-up redraft of the affected policy section(s) — smallest-possible edit, [verify] tags carried through, inline comments explaining WHY each change was made.
Output a Policy Redraft Memo. Write it to a new file named [policy-name]-proposed-redraft-[YYYY-MM-DD].md — never write to the source policy document.
Do NOT close the gap in the tracker. The gap closes when the redraft is applied AND approved, which is the policy owner's action.

This skill produces a proposal, not an edit. It writes to a new file with a clearly-marked draft filename. It never writes over a source policy document, and it never closes a gap in the tracker — the gap closes when the redraft is applied AND approved by the policy owner.

Matter context

Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /regulatory-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/regulatory-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.