Conduct Regulatory Compliance Audits
Regulatory compliance audits and implementation guidance for GDPR, HIPAA, SOC2, and PCI-DSS.
Why it matters
Ensure your software systems meet stringent regulatory requirements like GDPR, HIPAA, SOC2, and PCI-DSS. This skill provides comprehensive audits, actionable implementation guidance, and resources for achieving and maintaining compliance.
Outcomes
What it gets done
Assess compliance readiness for key regulations.
Generate compliance checklists and audit evidence.
Provide guidance on implementing and monitoring controls.
Create policy templates and training materials.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-security-compliance-compliance-check | bash Overview
Regulatory Compliance Check
Performs regulatory compliance audits (GDPR, HIPAA, SOC2, PCI-DSS) and produces gap analysis, technical controls, policy templates, and audit procedures. Use when assessing compliance readiness, building audit evidence, or designing compliance monitoring - not for legal counsel or formal certification.
What it does
Regulatory Compliance Check positions the assistant as a compliance expert specializing in regulatory requirements for software systems - GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards - performing comprehensive compliance audits and providing implementation guidance. Given requirements passed as $ARGUMENTS, output follows an eight-part format: a Compliance Assessment of current status across all applicable regulations, a Gap Analysis with severity-rated findings, a prioritized Implementation Plan, Technical Controls as actual code implementations, Policy Templates (privacy policies, consent forms, notices), Audit Procedures as continuous-monitoring scripts, Documentation of required records and evidence for auditors, and Training Materials for workforce compliance training.
When to use - and when NOT to
Use this skill when assessing compliance readiness for GDPR, HIPAA, SOC2, or PCI-DSS, building control checklists and audit evidence, or designing compliance monitoring and reporting. Do not use it when legal counsel or formal certification is needed, when scope approval or access to required evidence is missing, or when only a one-off security scan is wanted.
Inputs and outputs
Input is the compliance requirements passed as $ARGUMENTS - the applicable regulations, systems in scope, and evidence available. Output is the eight-part deliverable above, balancing compliance requirements with business operations and user experience. Two safety constraints are stated explicitly: never claim compliance without a formal audit, and protect sensitive data by limiting access to audit artifacts. If detailed patterns and examples are required, the skill points to resources/implementation-playbook.md.
Who it's for
Engineering and compliance teams building toward GDPR, HIPAA, SOC2, or PCI-DSS compliance who want a structured, evidence-generating process - assessment through documentation and workforce training - rather than a one-off scan or a claim of compliance without a formal audit behind it, and who already have scope approval and access to the required evidence.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.