When designing or updating an AI governance framework, establishing organizational policies for AI deployment, defining roles and responsibilities, or aligning AI practices with regulatory requirements (GDPR, AI Act, HIPAA, CCPA, etc.).
When NOT to use
For one-off compliance questions or tactical risk assessments. Use this skill when building or restructuring governance infrastructure, not for answering isolated compliance questions.
Instructions
Framework Design Process
Regulatory Landscape Identification
Identify all applicable regulations based on industry, geography, and use case
Document regulatory requirements for each rule
Map regulatory requirements to specific control families
Identify conflicting or overlapping requirements
Governance Architecture
Define AI governance roles: Chief AI Officer, Compliance Officer, Model Owner, Data Steward, etc.
Document decision authority: Who approves models for production? Who can modify deployed models?
Create escalation procedures for issues at Medium/High/Critical risk levels
Define approval chains for new models, data sources, and regulatory changes
Control Family Design
Regulatory Controls: Compliance with GDPR, AI Act, sector-specific rules
Scenario: A healthcare AI startup needs to deploy a patient risk prediction model. They operate in the US and EU, must comply with HIPAA, GDPR, and emerging AI Act requirements, and have limited compliance infrastructure.
Framework Design Output:
# AI Governance Framework - Healthcare AI Startup
## Regulatory Landscape
- **HIPAA Privacy Rule** — Patient data protection; requires de-identification, access controls, breach notification
- **HIPAA Security Rule** — Technical controls for PHI; audit logs, encryption, role-based access
- **GDPR** — Data minimization, consent, right to explanation, DPA with vendors
- **EU AI Act** — High-risk classification for medical AI; human oversight, documentation, bias monitoring
- **FDA Guidance** — Software as Medical Device (SaMD) regulatory expectations
## Governance Structure
- **Chief AI Officer** (executive sponsor)
- Approves production deployment
- Sets risk tolerance
- Owns escalation above compliance
- **Compliance Officer** (day-to-day)
- Maintains compliance checklist
- Conducts pre-deployment audits
- Manages vendor assessments
- **Model Owner** (ML team)
- Owns model development and performance
- Documents model card and decision log
- Responds to incidents
- **Data Officer** (data governance)
- Maintains consent records
- Ensures data lineage tracking
- Manages retention and deletion
## Control Families
### 1. Regulatory Compliance Control
**Requirement:** All AI systems must demonstrate compliance with HIPAA, GDPR, and AI Act.
**Procedure:**
- Map model to applicable regulations (HIPAA, GDPR, AI Act)
- Identify specific requirements for each regulation
- Design specific controls to address each requirement
- Document control design and evidence of implementation
**Evidence:** Regulatory mapping matrix, control documentation, audit checklist
### 2. Risk Assessment Control
**Requirement:** Every model must have completed risk assessment before production.
**Procedure:**
- Identify failure modes (accuracy failure, fairness drift, security attack, etc.)
- Quantify probability and impact
- Identify current controls and residual risk
- Document mitigation strategies and owners
- Escalate high/critical risks to leadership for approval
**Evidence:** Risk register, sign-off documentation, ongoing monitoring dashboard
### 3. Fairness & Bias Control
**Requirement:** Models must be audited for demographic disparities; disparities must be documented and mitigated.
**Procedure:**
- Identify protected classes (age, gender, race, ethnicity, disability status)
- Measure performance metrics by demographic group
- Analyze disparities > 5%; document root cause
- Design mitigations (data rebalancing, fairness constraints, sampling adjustments)
- Monitor fairness metrics in production
**Evidence:** Bias audit report, fairness dashboard, mitigation plan
### 4. Data Governance Control
**Requirement:** All training data must be sourced with proper consent; data lineage must be tracked; retention and deletion procedures must be in place.
**Procedure:**
- Audit data sources for consent (explicit consent vs. legitimate interest vs. contract)
- Document data lineage: source → transformation → model → inference
- Create data inventory with retention requirements
- Implement automated deletion procedures
- Log all data access
**Evidence:** Consent audit, data lineage diagram, deletion logs
### 5. Explainability Control
**Requirement:** Users and regulators must be able to understand model decisions.
**Procedure:**
- Document model architecture and training approach in model card
- Implement feature importance or SHAP analysis
- Prepare user-facing transparency disclosures
- Create decision log with explanations for key inferences
- Establish escalation procedure for unexplained decisions
**Evidence:** Model card, decision log, user transparency materials
### 6. Operational Control
**Requirement:** Access to models and data is restricted; changes are tracked; incidents are handled; systems can roll back.
**Procedure:**
- Define role-based access control (RBAC): who can deploy, modify, access data?
- Implement change control: all deployments logged and approved
- Establish monitoring dashboard for model performance and fairness drift
- Document rollback procedure; test quarterly
- Escalate incidents based on severity and regulatory impact
**Evidence:** Access control matrix, change log, monitoring dashboard, incident response plan
## Policies
### Policy 1: Model Deployment Approval
- All models require compliance checklist completion before production
- Compliance Officer conducts pre-deployment audit
- Model Owner certifies model card and documentation
- Chief AI Officer approves deployment
- No model reaches production without all three sign-offs
### Policy 2: Data Governance
- All training data must be sourced with documented consent
- Data lineage must be tracked from source to inference
- Data retention follows HIPAA (6 years) and GDPR (minimum necessary)
- Automated deletion procedures executed annually
- All data access logged and auditable
### Policy 3: Incident Response
- Model accuracy < 80%: notify Model Owner; assess in 24 hours
- Demographic disparities > 10%: escalate to Compliance Officer; develop mitigation in 48 hours
- Security breach or unauthorized access: escalate immediately to CISO; follow HIPAA breach notification rules
- Regulatory inquiry: escalate to General Counsel immediately; preserve audit trail
## Implementation Roadmap
- **Q1:** Establish governance roles, write core policies, create compliance checklist
- **Q2:** Implement risk assessment process for deployed models; audit fairness and data governance
- **Q3:** Build monitoring dashboard, establish incident response procedures
- **Q4:** Conduct full framework audit, document lessons learned, iterate
## Metrics
- **Compliance rate:** % of models with completed compliance checklist
- **Risk coverage:** % of identified risks with documented mitigations
- **Audit completion:** % of models audited for fairness and data governance
- **Incident response time:** time from incident detection to escalation (target: < 4 hours)
- **Documentation completeness:** all models have model card, risk register, decision log
Framework Components Checklist
When designing a framework, ensure you include:
Regulatory mapping (all applicable regulations identified and documented)
Training plan (how to communicate framework to organization)
Success Criteria
A complete compliance framework should:
Address all applicable regulations — Every regulation mapped to specific controls
Clarify decision authority — No ambiguity about who approves models, changes, escalations
Provide templates and procedures — Checklists, audit procedures, incident response runbooks ready-to-use
Enable measurement — Metrics and dashboards to track control effectiveness
Support continuous improvement — Regular reviews, updating for regulatory changes, incident learning
1---2name: compliance-framework-designer3description: Compliance Framework Designer4metadata:5 source: https://skillmd.com/skills/uitbreidenos/compliance-framework-designer6---7# Compliance Framework Designer89## When to activate1011When designing or updating an AI governance framework, establishing organizational policies for AI deployment, defining roles and responsibilities, or aligning AI practices with regulatory requirements (GDPR, AI Act, HIPAA, CCPA, etc.).1213## When NOT to use1415For one-off compliance questions or tactical risk assessments. Use this skill when building or restructuring governance infrastructure, not for answering isolated compliance questions.1617## Instructions1819### Framework Design Process20211. **Regulatory Landscape Identification**22 - Identify all applicable regulations based on industry, geography, and use case23 - Document regulatory requirements for each rule24 - Map regulatory requirements to specific control families25 - Identify conflicting or overlapping requirements26272. **Governance Architecture**28 - Define AI governance roles: Chief AI Officer, Compliance Officer, Model Owner, Data Steward, etc.29 - Document decision authority: Who approves models for production? Who can modify deployed models?30 - Create escalation procedures for issues at Medium/High/Critical risk levels31 - Define approval chains for new models, data sources, and regulatory changes32333. **Control Family Design**34 - **Regulatory Controls:** Compliance with GDPR, AI Act, sector-specific rules35 - **Risk Management Controls:** Risk assessment, monitoring, incident response36 - **Fairness & Bias Controls:** Bias audits, demographic monitoring, disparity tracking37 - **Data Governance Controls:** Consent tracking, lineage, retention, PII handling38 - **Explainability Controls:** Model interpretability, decision transparency, user communication39 - **Operational Controls:** Access management, change control, monitoring, rollback procedures40 - **Documentation Controls:** Model cards, decision logs, audit trails, incident records41424. **Policy Development**43 - Write governance policies addressing each control family44 - Include specific procedures and templates (checklists, audit procedures, incident response)45 - Define metrics for evaluating control effectiveness46 - Establish review cycles (annual, quarterly, or event-driven)47485. **Implementation Roadmap**49 - Prioritize control implementations based on risk and regulatory urgency50 - Define quick wins (high-impact, low-effort controls)51 - Establish timeline and resource requirements52 - Identify dependencies and critical path items5354### Framework Documentation Template5556Structure your framework as:57- Executive Summary: Purpose, scope, key principles58- Regulatory Mapping: Applicable regulations and coverage59- Governance Structure: Roles, responsibilities, decision authority60- Control Families: 6-8 core control areas with procedures61- Policies: Specific written policies (1-2 pages each)62- Operating Procedures: Detailed step-by-step procedures63- Templates: Pre-built checklists, audit procedures, decision logs64- Metrics: Key indicators of control effectiveness6566## Example6768**Scenario:** A healthcare AI startup needs to deploy a patient risk prediction model. They operate in the US and EU, must comply with HIPAA, GDPR, and emerging AI Act requirements, and have limited compliance infrastructure.6970**Framework Design Output:**7172```73# AI Governance Framework - Healthcare AI Startup7475## Regulatory Landscape76- **HIPAA Privacy Rule** — Patient data protection; requires de-identification, access controls, breach notification77- **HIPAA Security Rule** — Technical controls for PHI; audit logs, encryption, role-based access78- **GDPR** — Data minimization, consent, right to explanation, DPA with vendors79- **EU AI Act** — High-risk classification for medical AI; human oversight, documentation, bias monitoring80- **FDA Guidance** — Software as Medical Device (SaMD) regulatory expectations8182## Governance Structure83- **Chief AI Officer** (executive sponsor)84 - Approves production deployment85 - Sets risk tolerance86 - Owns escalation above compliance8788- **Compliance Officer** (day-to-day)89 - Maintains compliance checklist90 - Conducts pre-deployment audits91 - Manages vendor assessments9293- **Model Owner** (ML team)94 - Owns model development and performance95 - Documents model card and decision log96 - Responds to incidents9798- **Data Officer** (data governance)99 - Maintains consent records100 - Ensures data lineage tracking101 - Manages retention and deletion102103## Control Families104105### 1. Regulatory Compliance Control106**Requirement:** All AI systems must demonstrate compliance with HIPAA, GDPR, and AI Act.107**Procedure:**108- Map model to applicable regulations (HIPAA, GDPR, AI Act)109- Identify specific requirements for each regulation110- Design specific controls to address each requirement111- Document control design and evidence of implementation112113**Evidence:** Regulatory mapping matrix, control documentation, audit checklist114115### 2. Risk Assessment Control116**Requirement:** Every model must have completed risk assessment before production.117**Procedure:**118- Identify failure modes (accuracy failure, fairness drift, security attack, etc.)119- Quantify probability and impact120- Identify current controls and residual risk121- Document mitigation strategies and owners122- Escalate high/critical risks to leadership for approval123124**Evidence:** Risk register, sign-off documentation, ongoing monitoring dashboard125126### 3. Fairness & Bias Control127**Requirement:** Models must be audited for demographic disparities; disparities must be documented and mitigated.128**Procedure:**129- Identify protected classes (age, gender, race, ethnicity, disability status)130- Measure performance metrics by demographic group131- Analyze disparities > 5%; document root cause132- Design mitigations (data rebalancing, fairness constraints, sampling adjustments)133- Monitor fairness metrics in production134135**Evidence:** Bias audit report, fairness dashboard, mitigation plan136137### 4. Data Governance Control138**Requirement:** All training data must be sourced with proper consent; data lineage must be tracked; retention and deletion procedures must be in place.139**Procedure:**140- Audit data sources for consent (explicit consent vs. legitimate interest vs. contract)141- Document data lineage: source → transformation → model → inference142- Create data inventory with retention requirements143- Implement automated deletion procedures144- Log all data access145146**Evidence:** Consent audit, data lineage diagram, deletion logs147148### 5. Explainability Control149**Requirement:** Users and regulators must be able to understand model decisions.150**Procedure:**151- Document model architecture and training approach in model card152- Implement feature importance or SHAP analysis153- Prepare user-facing transparency disclosures154- Create decision log with explanations for key inferences155- Establish escalation procedure for unexplained decisions156157**Evidence:** Model card, decision log, user transparency materials158159### 6. Operational Control160**Requirement:** Access to models and data is restricted; changes are tracked; incidents are handled; systems can roll back.161**Procedure:**162- Define role-based access control (RBAC): who can deploy, modify, access data?163- Implement change control: all deployments logged and approved164- Establish monitoring dashboard for model performance and fairness drift165- Document rollback procedure; test quarterly166- Escalate incidents based on severity and regulatory impact167168**Evidence:** Access control matrix, change log, monitoring dashboard, incident response plan169170## Policies171172### Policy 1: Model Deployment Approval173- All models require compliance checklist completion before production174- Compliance Officer conducts pre-deployment audit175- Model Owner certifies model card and documentation176- Chief AI Officer approves deployment177- No model reaches production without all three sign-offs178179### Policy 2: Data Governance180- All training data must be sourced with documented consent181- Data lineage must be tracked from source to inference182- Data retention follows HIPAA (6 years) and GDPR (minimum necessary)183- Automated deletion procedures executed annually184- All data access logged and auditable185186### Policy 3: Incident Response187- Model accuracy < 80%: notify Model Owner; assess in 24 hours188- Demographic disparities > 10%: escalate to Compliance Officer; develop mitigation in 48 hours189- Security breach or unauthorized access: escalate immediately to CISO; follow HIPAA breach notification rules190- Regulatory inquiry: escalate to General Counsel immediately; preserve audit trail191192## Implementation Roadmap193- **Q1:** Establish governance roles, write core policies, create compliance checklist194- **Q2:** Implement risk assessment process for deployed models; audit fairness and data governance195- **Q3:** Build monitoring dashboard, establish incident response procedures196- **Q4:** Conduct full framework audit, document lessons learned, iterate197198## Metrics199- **Compliance rate:** % of models with completed compliance checklist200- **Risk coverage:** % of identified risks with documented mitigations201- **Audit completion:** % of models audited for fairness and data governance202- **Incident response time:** time from incident detection to escalation (target: < 4 hours)203- **Documentation completeness:** all models have model card, risk register, decision log204```205206---207208## Framework Components Checklist209210When designing a framework, ensure you include:211212- [ ] Regulatory mapping (all applicable regulations identified and documented)213- [ ] Governance structure (roles, responsibilities, decision authority)214- [ ] Control families (6-8 core areas: compliance, risk, fairness, data, explainability, operations, documentation, vendor management)215- [ ] Specific policies (written governance policies; 2-3 pages each)216- [ ] Operating procedures (step-by-step procedures with templates)217- [ ] Escalation matrix (response procedures and timeline by risk level)218- [ ] Compliance checklist (pre-deployment validation)219- [ ] Metrics and KPIs (how to measure control effectiveness)220- [ ] Implementation roadmap (timeline, dependencies, resource requirements)221- [ ] Training plan (how to communicate framework to organization)222223---224225## Success Criteria226227A complete compliance framework should:2282291. **Address all applicable regulations** — Every regulation mapped to specific controls2302. **Clarify decision authority** — No ambiguity about who approves models, changes, escalations2313. **Provide templates and procedures** — Checklists, audit procedures, incident response runbooks ready-to-use2324. **Enable measurement** — Metrics and dashboards to track control effectiveness2335. **Support continuous improvement** — Regular reviews, updating for regulatory changes, incident learning
Run npx get-skill add uitbreidenos/compliance-framework-designer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Compliance Framework Designer It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
UitbreidenOS (@uitbreidenos) published this skill. Their other Agent Skills are listed on their SkillMD profile.