reg-gap-checklisted

# Regulatory Gap Check: find the challenge before the regulator does Most payments product work dies in review, not in build. The PM ships a spec, then legal, compliance, the scheme, or the central bank asks the question nobody wrote down, and the roadmap slips a quarter. This skill runs the challenge in advance. ## Files this skill drives - [../../modules/regulated/README.md](../../modules/regulated/README.md), which explains when the regulated overlay activates and names the canonical source - [../../modules/regulated/templates/regulated-ai-prd-template.md](../../modules/regulated/templates/regulated-ai-prd-template.md), the byte-exact template whose section 0 and Appendix A hold the repository's only verified regulatory citations - [../../modules/regulated/SKILL.md](../../modules/regulated/SKILL.md), the authoring procedure for a regulated AI PRD - Findings land in [../../templates/execution/risk-register.md](../../templates/execution/risk-register.md) and, where an assessment is warranted, trigger [../../templates/operate/compliance-impact-assessment.md](../../templates/operate/compliance-impact-assessment.md) ## The citation rule, before anything else This skill maps gaps; it does not write regulation. The only regulator text this repository vouches for lives inside `modules/regulated/`, where every citation carries the date it was verified against primary text. When a gap touches an instrument covered there, cite it by pointing into the module. When a gap touches a