Regulatory Change Tracking Skill
Trigger Conditions
- •Quarterly compliance review cycle
- •New regulatory advisory or rule change identified
- •Compliance service code changes
- •User invokes with "regulatory update" or "regulatory-change-tracking"
Input Contract
- •Optional: Specific regulation or advisory to assess
Output Contract
- •Regulation-by-regulation assessment of current compliance
- •Gap analysis for any new requirements
- •Implementation roadmap for remediation
- •Updated plan with new compliance tasks
Tool Permissions
- •Read: All source files, compliance plans, regulatory rule files (104, 107-109)
- •Write: Plan files, compliance assessment documents
- •Search: Grep for regulatory constants, threshold values, compliance functions
Execution Steps
- •Inventory current regulations: List all regulations referenced in rules 104, 107-109
- •Check implementation: For each regulation, verify the codebase implements required controls
- •Gap analysis: Compare current implementation against latest requirements
- •Impact assessment: For each gap, estimate implementation effort and priority
- •Update plan: Add new todos to the compliance plan for any gaps found
Key Regulations Tracked
- •NACHA Operating Rules — ACH processing requirements