gaps

To track regulatory gaps, this Skill reads a local YAML gap-tracker file, lists open policy and procedure gaps, and prioritizes them based on importance, age, ownership, and due dates to produce an ordered report for remediation tracking.

You log risk acceptance decisions by using the --accept argument with a specific gap ID. This records the justification and responsible authority directly into your YAML gap-tracker file for compliance recordkeeping.

The best way to document closure approvals is using the --close argument with a targeted gap ID. This logs the remediation solutions and approval details into the YAML tracker, closing the regulatory gap.

No, this Skill does not discover validation requirements automatically. It relies on a separate reference skill, gap-surfacer, to handle substantive gap discovery and validation to prevent overdue misclassification and unsupported legal conclusions.

Yes, you can use a YAML file for compliance remediation tracking. The Skill reads and updates a local YAML file to manage regulatory monitoring operations, document risk acceptance, and record closure approvals for specific gap IDs.

Regulatory monitoring operations miss risk acceptance records if decisions are not formally logged. This Skill prevents missing records by using the --accept argument to store justifications and responsible authorities for specific gap IDs in your tracker.