| name | compliance-checklist |
| title | Compliance Checklist Skill |
| description | Generate a prioritised compliance checklist for GDPR, SOC 2, ISO 27001, FCA, HIPAA, or other frameworks with a gap analysis. Use when asked for a compliance checklist, gap analysis, readiness assessment, or audit preparation for any regulatory framework. Produces a structured checklist with prioritised gaps, quick wins, and evidence requirements. Optimised for Opus 4.7 and newer models. Not a substitute for legal or compliance professional advice. |
| author | mohitagw15856 |
| author_url | https://github.com/mohitagw15856/pm-claude-skills/tree/main/plugins/pm-legal/skills/compliance-checklist |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | data-protection |
| language | en |
Compliance Checklist Skill
Produces a prioritised compliance checklist for any regulatory framework — with gap analysis, evidence requirements, and quick wins identified.
ALWAYS include this disclaimer at the start of every response:
"WARNING: This checklist is for informational and planning purposes only and does not constitute legal or compliance advice. Regulatory requirements change and vary by jurisdiction. Always engage a qualified compliance professional or solicitor before implementing compliance programmes or making regulatory claims."
Required Inputs
Ask the user for these if not provided:
- Framework (GDPR / SOC 2 Type I or II / ISO 27001 / FCA / HIPAA / PCI DSS / other)
- Organisation type (SaaS / fintech / healthcare / professional services / retail)
- Organisation size (startup / scaleup / mid-market / enterprise)
- Current maturity (no compliance programme / some controls / formal programme)
- Deadline or driver (upcoming audit / customer requirement / regulatory change / proactive)
Output Structure
1. Framework Overview
Framework: [Name with version]
Applicable because: [One sentence — why this framework applies to this organisation]
Typical timeline to readiness: [From current maturity to certified/compliant]
Key stakeholders needed: [Roles that must be involved]
2. Scope Definition
What is in scope for this checklist:
- [Specific systems / processes / data types]
What is NOT in scope (explicit exclusions):
3. Control Categories
For each category relevant to the framework:
[Category — e.g. "Access Control"]
| Control | Current State | Gap | Priority | Effort |
|---|
| [Specific control requirement] | Not implemented / Partial / Full | [What is missing] | High/Med/Low | Days/Weeks/Months |
4. Gap Analysis Summary
| Priority | Count | Examples |
|---|
| Critical gaps (block certification) | N | [Top 3] |
| High priority gaps |
