policy-redraft

To draft a policy redraft, provide the identified gap description, current approved policy text, and relevant UK rule text. The skill outputs a marked-up redline proposal with inline rationale to a new draft file, ensuring unapproved edits are never applied to source documents.

Yes, you can produce a marked-up redline from a gap tracker entry. The skill enforces proposal-only output to a new draft file, keeping original policy text untouched while generating smallest-possible edits with inline explanations for each change.

Rule status verification checks the currency of relevant UK rule text during policy redrafting. When status cannot be confirmed, the skill displays clear unverified banners and preserves existing [verify] tags for dates, citations, and thresholds.

The best way to propose smallest-possible edits is using a gap-to-redraft workflow that generates tightly scoped redlined sections. Each edit includes inline rationale explaining why the change is made, ensuring changes remain minimal and reviewer-ready.

Yes, policy redrafting supports policy-diff handoffs. The workflow accepts a described diff or gap ID from gap analysis tooling, pairs it with approved policy and UK rule text, and produces a marked-up proposed redraft for downstream review.

When UK regulation rule status cannot be confirmed during compliance drafting, the skill outputs clear unverified banners and maintains [verify] tagging on specific dates, citations, and thresholds to flag uncertainty for human reviewers.