gap-surfacer

Track regulatory policy gaps with due dates, owners, and remediation status.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents regulatory policy gaps from getting lost by tracking open requirements, aging them against due dates, and routing ownership for closure.

Core Features & Use Cases

  • Gap tracking for regulatory requirements: Maintains a gap tracker (with remediation status, owner, due date, and verification state) for both compliance gaps and pre-rule tracking artifacts.
  • Overdue and due-soon reporting with safety semantics: Flags overdue only when the rule is verified, and uses “review needed” routing for unverified rules to avoid incorrect escalations.
  • Owner assignment and notifications with per-send confirmation: Sends Slack DM notifications to gap owners only after showing an explicit preview and receiving an explicit user confirmation.

Quick Start

Use gap-surfacer to ingest policy-diff gaps and generate a status report while ensuring any Slack notifications require per-send confirmation.

Frequently Asked Questions about gap-surfacer

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

FAQPage Schema
How do I track regulatory policy gaps to prevent missed compliance deadlines?

You can track regulatory policy gaps by ingesting policy-diff outputs into a gap tracker that maintains remediation status, owner assignment, and due dates to prevent missed deadlines and lost follow-ups.

How do I send Slack notifications to gap owners without accidental escalations?

Send Slack notifications to gap owners safely by using per-send user confirmation gating that requires an explicit approval after showing a notification preview before any message is delivered.

How does overdue classification work for unverified regulatory rules?

Overdue classification flags overdue status only when the rule is verified, and uses 'review needed' routing for unverified rules to avoid incorrect escalations and false compliance alerts.

Can I manage pre-rule tracking and compliance gaps in the same tracker?

Yes, you can manage pre-rule watch and comment-decision items separately alongside compliance gaps, applying de-duplication rules and verified-vs-unverified overdue classification logic within the same state management.

What is the best way to generate due-soon and overdue status reports for compliance gaps?

Generate due-soon and overdue status reports by aging open requirements against their due dates using a gap tracker that distinguishes verified from unverified rules to ensure safety semantics.