[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7388M6CS2KHB475MCDSXR2M":3,"skill-same:01M7388M6CS2KHB475MCDSXR2M":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M7388M6CS2KHB475MCDSXR2M","design-compliance-architecture",null,"Design a compliance architecture that maps applicable regulations to computerized systems. Covers system inventory, criticality classification (GxP-critical, GxP-supporting, non-GxP), GAMP 5 category assignment, regulatory requirements traceability, and governance structure definition. Use when establishing a new regulated facility, formalising compliance across multiple systems, addressing a regulatory gap analysis, harmonising compliance after mergers or reorganisations, or preparing a site master file that references computerized systems.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-compliance-architecture\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: design-compliance-architecture\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-04-23\"\ndescription: >\n  Design a compliance architecture that maps applicable regulations to\n  computerized systems. Covers system inventory, criticality classification\n  (GxP-critical, GxP-supporting, non-GxP), GAMP 5 category assignment,\n  regulatory requirements traceability, and governance structure definition.\n  Use when establishing a new regulated facility, formalising compliance\n  across multiple systems, addressing a regulatory gap analysis, harmonising\n  compliance after mergers or reorganisations, or preparing a site master\n  file that references computerized systems.\nlicense: MIT\nallowed-tools: Read Write Edit Bash Grep Glob\nmetadata:\n  author: Philipp Thoss\n  version: \"1.0\"\n  domain: compliance\n  complexity: advanced\n  language: multi\n  tags: gxp, compliance, architecture, regulatory, gamp-5, governance\n---\n\n# Design Compliance Architecture\n\nEstablish the top-level compliance framework that maps regulations to systems, classifies criticality, and defines governance for a regulated environment.\n\n## When to Use\n\n- A new regulated facility, department, or programme is being established\n- An existing organisation needs to formalise its compliance posture across multiple systems\n- A regulatory gap analysis reveals missing system classification or validation strategy\n- Mergers, acquisitions, or reorganisations require harmonising compliance across entities\n- Preparing a site master file or quality manual that references computerized systems\n\n## Inputs\n\n- **Required**: List of computerized systems in scope (name, purpose, vendor\u002Fcustom)\n- **Required**: Applicable regulatory frameworks (21 CFR Part 11, EU Annex 11, GMP, GLP, GCP, ICH Q7, ICH Q10)\n- **Required**: Organisational context (department, site, product types)\n- **Optional**: Existing validation master plan or quality manual\n- **Optional**: Previous audit findings or regulatory inspection observations\n- **Optional**: Organisational chart with quality and IT reporting lines\n\n## Procedure\n\n### Step 1: Build the System Inventory\n\nCreate a comprehensive inventory of all computerized systems:\n\n```markdown\n# System Inventory\n## Document ID: SI-[SITE]-[YYYY]-[NNN]\n\n| ID | System Name | Version | Vendor | Purpose | Department | Data Types | Users |\n|----|-------------|---------|--------|---------|------------|------------|-------|\n| SYS-001 | LabWare LIMS | 8.1 | LabWare Inc. | Sample management and testing | QC | Test results, COA | 45 |\n| SYS-002 | SAP ERP | S\u002F4HANA | SAP SE | Batch release and inventory | Production | Batch records, BOM | 120 |\n| SYS-003 | Custom R\u002FShiny | 2.1.0 | Internal | Statistical analysis | Biostatistics | Clinical data | 8 |\n| SYS-004 | Windows Server | 2022 | Microsoft | File server | IT | Documents | 200 |\n```\n\n**Got:** Every system that creates, modifies, stores, retrieves, or transmits GxP-relevant data is listed.\n**If fail:** If system owners cannot provide complete information, document the gap and schedule a discovery workshop. Missing systems are a critical compliance risk.\n\n### Step 2: Classify System Criticality\n\nAssign each system a criticality tier:\n\n```markdown\n# System Criticality Classification\n## Document ID: SCC-[SITE]-[YYYY]-[NNN]\n\n### Classification Criteria\n\n| Tier | Definition | Validation Required | Examples |\n|------|-----------|-------------------|----------|\n| **GxP-Critical** | Directly impacts product quality, patient safety, or data integrity. Generates or processes GxP records. | Full CSV per GAMP 5 | LIMS, ERP (batch), CDMS, MES |\n| **GxP-Supporting** | Supports GxP processes but does not directly generate GxP records. Failure has indirect impact. | Risk-based qualification | Email, document management, scheduling |\n| **Non-GxP** | No impact on product quality, safety, or data integrity. | IT standard controls only | HR systems, cafeteria, general web |\n\n### System Classification Matrix\n\n| System ID | System | Tier | Rationale |\n|-----------|--------|------|-----------|\n| SYS-001 | LabWare LIMS | GxP-Critical | Generates test results used for batch release |\n| SYS-002 | SAP ERP | GxP-Critical | Manages batch records and material traceability |\n| SYS-003 | R\u002FShiny App | GxP-Critical | Performs statistical analysis for regulatory submissions |\n| SYS-004 | Windows Server | GxP-Supporting | Stores controlled documents but does not generate GxP data |\n```\n\n**Got:** Every system has a tier assignment with documented rationale.\n**If fail:** If a system's criticality is disputed, escalate to the quality council. When in doubt, classify one tier higher and reassess after a formal risk assessment.\n\n### Step 3: Assign GAMP 5 Software Categories\n\nFor each GxP-Critical and GxP-Supporting system, assign the GAMP 5 category:\n\n```markdown\n# GAMP 5 Category Assignment\n\n| System ID | System | GAMP Category | Rationale | Validation Effort |\n|-----------|--------|---------------|-----------|-------------------|\n| SYS-001 | LabWare LIMS | 4 — Configured Product | COTS with extensive workflow configuration | Medium-High |\n| SYS-002 | SAP ERP | 4 — Configured Product | COTS with custom transactions | Medium-High |\n| SYS-003 | R\u002FShiny App | 5 — Custom Application | Internally developed | High — Full lifecycle |\n| SYS-004 | Windows Server | 1 — Infrastructure | Operating system, no custom configuration | Low — Verify installation |\n```\n\nCategory reference:\n- **Category 1**: Infrastructure (OS, firmware) — verify installation\n- **Category 3**: Non-configured COTS — verify functionality as-is\n- **Category 4**: Configured product — verify all configurations\n- **Category 5**: Custom application — full lifecycle validation\n\n**Got:** Category assignment aligns with how the system is used, not what it is.\n**If fail:** If a system spans categories (e.g., COTS with custom add-ons), classify the custom portions as Category 5 and the base as Category 4.\n\n### Step 4: Map Regulatory Requirements to Systems\n\nCreate a regulatory requirements traceability matrix:\n\n```markdown\n# Regulatory Requirements Traceability Matrix\n## Document ID: RRTM-[SITE]-[YYYY]-[NNN]\n\n| Regulation | Clause | Requirement | Applicable Systems | Control Type |\n|-----------|--------|-------------|-------------------|--------------|\n| 21 CFR 11 | 11.10(a) | Validation | SYS-001, SYS-002, SYS-003 | Procedural + Technical |\n| 21 CFR 11 | 11.10(d) | Access controls | SYS-001, SYS-002, SYS-003, SYS-004 | Technical |\n| 21 CFR 11 | 11.10(e) | Audit trail | SYS-001, SYS-002, SYS-003 | Technical |\n| 21 CFR 11 | 11.50 | Signature manifestation | SYS-001, SYS-002 | Technical |\n| EU Annex 11 | §4 | Validation | SYS-001, SYS-002, SYS-003 | Procedural + Technical |\n| EU Annex 11 | §7 | Data storage and backup | All | Technical |\n| EU Annex 11 | §9 | Audit trail | SYS-001, SYS-002, SYS-003 | Technical |\n| EU Annex 11 | §12 | Security and access | All | Technical |\n| ICH Q10 | §3.2 | Change management | All GxP-Critical | Procedural |\n| ICH Q10 | §1.8 | Knowledge management | SYS-001, SYS-003 | Procedural |\n```\n\n**Got:** Every applicable regulatory clause maps to at least one system, and every GxP-Critical system maps to the relevant regulatory clauses.\n**If fail:** Unmapped clauses represent compliance gaps. Create a remediation plan with timelines for each gap.\n\n### Step 5: Define Validation Strategy Per System\n\nBased on criticality, category, and regulatory mapping:\n\n```markdown\n# Validation Strategy Summary\n\n| System | Category | Criticality | Validation Approach | Key Deliverables |\n|--------|----------|------------|--------------------|--------------------|\n| LabWare LIMS | 4 | Critical | Prospective CSV | URS, RA, VP, IQ, OQ, PQ, TM, VSR |\n| SAP ERP | 4 | Critical | Prospective CSV | URS, RA, VP, IQ, OQ, TM, VSR |\n| R\u002FShiny App | 5 | Critical | Prospective CSV + code review | URS, RA, VP, IQ, OQ, PQ, TM, VSR, code audit |\n| Windows Server | 1 | Supporting | Installation qualification | IQ checklist |\n```\n\nAbbreviations: URS (User Requirements), RA (Risk Assessment), VP (Validation Plan), IQ\u002FOQ\u002FPQ (Installation\u002FOperational\u002FPerformance Qualification), TM (Traceability Matrix), VSR (Validation Summary Report).\n\n**Got:** Validation effort is proportional to risk — Category 5 GxP-Critical systems get full lifecycle; Category 1 infrastructure gets streamlined IQ.\n**If fail:** If stakeholders push for reduced validation of critical systems, document the risk acceptance with QA sign-off.\n\n### Step 6: Design Governance Structure\n\nDefine the organisational framework for sustaining compliance:\n\n```markdown\n# Compliance Governance Structure\n\n## Roles and Responsibilities\n| Role | Responsibility | Authority |\n|------|---------------|-----------|\n| Quality Director | Overall compliance accountability | Approve validation strategies, accept risks |\n| System Owner | Day-to-day system compliance | Approve changes, ensure validated state |\n| Validation Lead | Plan and coordinate validation activities | Define validation scope and approach |\n| IT Operations | Technical infrastructure and security | Implement technical controls |\n| QA Reviewer | Independent review of validation deliverables | Accept or reject validation evidence |\n\n## Governance Committees\n| Committee | Frequency | Purpose | Members |\n|-----------|-----------|---------|---------|\n| Change Control Board | Weekly | Review and approve system changes | System owners, QA, IT, validation |\n| Periodic Review Committee | Quarterly | Review system compliance status | Quality director, system owners, QA |\n| Audit Programme Committee | Annual | Plan internal audit schedule | Quality director, lead auditor, QA |\n\n## Escalation Matrix\n| Issue | First Escalation | Second Escalation | Timeline |\n|-------|-----------------|-------------------|----------|\n| Critical audit finding | System Owner → QA Director | QA Director → Site Director | 24 hours |\n| Validated state breach | Validation Lead → System Owner | System Owner → Quality Director | 48 hours |\n| Data integrity incident | System Owner → QA Director | QA Director → Regulatory Affairs | 24 hours |\n```\n\n**Got:** Clear accountability for every compliance activity with no orphaned responsibilities.\n**If fail:** If roles overlap or are unassigned, convene a RACI workshop to resolve. Ambiguous ownership is a recurring regulatory citation.\n\n### Step 7: Compile the Compliance Architecture Document\n\nAssemble all components into the master document:\n\n```markdown\n# Compliance Architecture\n## Document ID: CA-[SITE]-[YYYY]-[NNN]\n## Version: 1.0\n\n### 1. Purpose and Scope\n[Organisation, site, product scope, regulatory scope]\n\n### 2. System Inventory\n[From Step 1]\n\n### 3. Criticality Classification\n[From Step 2]\n\n### 4. GAMP 5 Category Assignments\n[From Step 3]\n\n### 5. Regulatory Requirements Traceability\n[From Step 4]\n\n### 6. Validation Strategy\n[From Step 5]\n\n### 7. Governance Structure\n[From Step 6]\n\n### 8. Periodic Review Schedule\n- System inventory refresh: Annual\n- Criticality re-assessment: When new systems added or regulations change\n- Regulatory mapping update: When new guidance issued\n- Governance review: Annual or after organisational change\n\n### 9. Approval\n| Role | Name | Signature | Date |\n|------|------|-----------|------|\n| Quality Director | | | |\n| IT Director | | | |\n| Regulatory Affairs | | | |\n```\n\n**Got:** A single document that serves as the compliance blueprint for the entire regulated environment.\n**If fail:** If the document exceeds practical size, create a master document with references to subsidiary documents per system or domain.\n\n## Validation\n\n- [ ] System inventory includes every system that handles GxP data\n- [ ] Every system has a criticality tier with documented rationale\n- [ ] GAMP 5 categories assigned to all GxP-Critical and GxP-Supporting systems\n- [ ] Regulatory requirements traceability matrix covers all applicable clauses\n- [ ] Every GxP-Critical system has a defined validation strategy\n- [ ] Governance structure defines roles, committees, and escalation paths\n- [ ] All documents have unique IDs and version control\n- [ ] Compliance architecture document is approved by quality and IT leadership\n\n## Pitfalls\n\n- **Incomplete inventory**: Missing systems are invisible to compliance. Use network scans, software asset management tools, and department interviews — not asking IT.\n- **Binary thinking**: Systems are not \"GxP\" or \"not GxP.\" The three-tier model (Critical, Supporting, Non-GxP) avoids both over-validation and under-validation.\n- **Category confusion**: GAMP 5 category describes what the software IS, but validation effort should reflect how it is USED. A Category 4 system used for batch release needs more testing than a Category 4 system used for scheduling.\n- **Static architecture**: The compliance architecture is a living document. New systems, regulatory changes, and audit findings all require updates.\n- **Governance without teeth**: Committees that exist on paper but never meet provide no compliance value. Define meeting cadence and quorum requirements.\n\n## Related Skills\n\n- `perform-csv-assessment` — execute the validation strategy defined here for individual systems\n- `manage-change-control` — operationalise the change control process defined in governance\n- `implement-electronic-signatures` — implement e-signature controls mapped in the regulatory matrix\n- `prepare-inspection-readiness` — use this architecture as the foundation for inspection preparation\n- `conduct-gxp-audit` — audit against the compliance architecture as the baseline\n","# Design Compliance Architecture\n\nEstablish the top-level compliance framework that maps regulations to systems, classifies criticality, and defines governance for a regulated environment.\n\n## When to Use\n\n- A new regulated facility, department, or programme is being established\n- An existing organisation needs to formalise its compliance posture across multiple systems\n- A regulatory gap analysis reveals missing system classification or validation strategy\n- Mergers, acquisitions, or reorganisations require harmonising compliance across entities\n- Preparing a site master file or quality manual that references computerized systems\n\n## Inputs\n\n- **Required**: List of computerized systems in scope (name, purpose, vendor\u002Fcustom)\n- **Required**: Applicable regulatory frameworks (21 CFR Part 11, EU Annex 11, GMP, GLP, GCP, ICH Q7, ICH Q10)\n- **Required**: Organisational context (department, site, product types)\n- **Optional**: Existing validation master plan or quality manual\n- **Optional**: Previous audit findings or regulatory inspection observations\n- **Optional**: Organisational chart with quality and IT reporting lines\n\n## Procedure\n\n### Step 1: Build the System Inventory\n\nCreate a comprehensive inventory of all computerized systems:\n\n```markdown\n# System Inventory\n## Document ID: SI-[SITE]-[YYYY]-[NNN]\n\n| ID | System Name | Version | Vendor | Purpose | Department | Data Types | Users |\n|----|-------------|---------|--------|---------|------------|------------|-------|\n| SYS-001 | LabWare LIMS | 8.1 | LabWare Inc. | Sample management and testing | QC | Test results, COA | 45 |\n| SYS-002 | SAP ERP | S\u002F4HANA | SAP SE | Batch release and inventory | Production | Batch records, BOM | 120 |\n| SYS-003 | Custom R\u002FShiny | 2.1.0 | Internal | Statistical analysis | Biostatistics | Clinical data | 8 |\n| SYS-004 | Windows Server | 2022 | Microsoft | File server | IT | Documents | 200 |\n```\n\n**Got:** Every system that creates, modifies, stores, retrieves, or transmits GxP-relevant data is listed.\n**If fail:** If system owners cannot provide complete information, document the gap and schedule a discovery workshop. Missing systems are a critical compliance risk.\n\n### Step 2: Classify System Criticality\n\nAssign each system a criticality tier:\n\n```markdown\n# System Criticality Classification\n## Document ID: SCC-[SITE]-[YYYY]-[NNN]\n\n### Classification Criteria\n\n| Tier | Definition | Validation Required | Examples |\n|------|-----------|-------------------|----------|\n| **GxP-Critical** | Directly impacts product quality, patient safety, or data integrity. Generates or processes GxP records. | Full CSV per GAMP 5 | LIMS, ERP (batch), CDMS, MES |\n| **GxP-Supporting** | Supports GxP processes but does not directly generate GxP records. Failure has indirect impact. | Risk-based qualification | Email, document management, scheduling |\n| **Non-GxP** | No impact on product quality, safety, or data integrity. | IT standard controls only | HR systems, cafeteria, general web |\n\n### System Classification Matrix\n\n| System ID | System | Tier | Rationale |\n|-----------|--------|------|-----------|\n| SYS-001 | LabWare LIMS | GxP-Critical | Generates test results used for batch release |\n| SYS-002 | SAP ERP | GxP-Critical | Manages batch records and material traceability |\n| SYS-003 | R\u002FShiny App | GxP-Critical | Performs statistical analysis for regulatory submissions |\n| SYS-004 | Windows Server | GxP-Supporting | Stores controlled documents but does not generate GxP data |\n```\n\n**Got:** Every system has a tier assignment with documented rationale.\n**If fail:** If a system's criticality is disputed, escalate to the quality council. When in doubt, classify one tier higher and reassess after a formal risk assessment.\n\n### Step 3: Assign GAMP 5 Software Categories\n\nFor each GxP-Critical and GxP-Supporting system, assign the GAMP 5 category:\n\n```markdown\n# GAMP 5 Category Assignment\n\n| System ID | System | GAMP Category | Rationale | Validation Effort |\n|-----------|--------|---------------|-----------|-------------------|\n| SYS-001 | LabWare LIMS | 4 — Configured Product | COTS with extensive workflow configuration | Medium-High |\n| SYS-002 | SAP ERP | 4 — Configured Product | COTS with custom transactions | Medium-High |\n| SYS-003 | R\u002FShiny App | 5 — Custom Application | Internally developed | High — Full lifecycle |\n| SYS-004 | Windows Server | 1 — Infrastructure | Operating system, no custom configuration | Low — Verify installation |\n```\n\nCategory reference:\n- **Category 1**: Infrastructure (OS, firmware) — verify installation\n- **Category 3**: Non-configured COTS — verify functionality as-is\n- **Category 4**: Configured product — verify all configurations\n- **Category 5**: Custom application — full lifecycle validation\n\n**Got:** Category assignment aligns with how the system is used, not what it is.\n**If fail:** If a system spans categories (e.g., COTS with custom add-ons), classify the custom portions as Category 5 and the base as Category 4.\n\n### Step 4: Map Regulatory Requirements to Systems\n\nCreate a regulatory requirements traceability matrix:\n\n```markdown\n# Regulatory Requirements Traceability Matrix\n## Document ID: RRTM-[SITE]-[YYYY]-[NNN]\n\n| Regulation | Clause | Requirement | Applicable Systems | Control Type |\n|-----------|--------|-------------|-------------------|--------------|\n| 21 CFR 11 | 11.10(a) | Validation | SYS-001, SYS-002, SYS-003 | Procedural + Technical |\n| 21 CFR 11 | 11.10(d) | Access controls | SYS-001, SYS-002, SYS-003, SYS-004 | Technical |\n| 21 CFR 11 | 11.10(e) | Audit trail | SYS-001, SYS-002, SYS-003 | Technical |\n| 21 CFR 11 | 11.50 | Signature manifestation | SYS-001, SYS-002 | Technical |\n| EU Annex 11 | §4 | Validation | SYS-001, SYS-002, SYS-003 | Procedural + Technical |\n| EU Annex 11 | §7 | Data storage and backup | All | Technical |\n| EU Annex 11 | §9 | Audit trail | SYS-001, SYS-002, SYS-003 | Technical |\n| EU Annex 11 | §12 | Security and access | All | Technical |\n| ICH Q10 | §3.2 | Change management | All GxP-Critical | Procedural |\n| ICH Q10 | §1.8 | Knowledge management | SYS-001, SYS-003 | Procedural |\n```\n\n**Got:** Every applicable regulatory clause maps to at least one system, and every GxP-Critical system maps to the relevant regulatory clauses.\n**If fail:** Unmapped clauses represent compliance gaps. Create a remediation plan with timelines for each gap.\n\n### Step 5: Define Validation Strategy Per System\n\nBased on criticality, category, and regulatory mapping:\n\n```markdown\n# Validation Strategy Summary\n\n| System | Category | Criticality | Validation Approach | Key Deliverables |\n|--------|----------|------------|--------------------|--------------------|\n| LabWare LIMS | 4 | Critical | Prospective CSV | URS, RA, VP, IQ, OQ, PQ, TM, VSR |\n| SAP ERP | 4 | Critical | Prospective CSV | URS, RA, VP, IQ, OQ, TM, VSR |\n| R\u002FShiny App | 5 | Critical | Prospective CSV + code review | URS, RA, VP, IQ, OQ, PQ, TM, VSR, code audit |\n| Windows Server | 1 | Supporting | Installation qualification | IQ checklist |\n```\n\nAbbreviations: URS (User Requirements), RA (Risk Assessment), VP (Validation Plan), IQ\u002FOQ\u002FPQ (Installation\u002FOperational\u002FPerformance Qualification), TM (Traceability Matrix), VSR (Validation Summary Report).\n\n**Got:** Validation effort is proportional to risk — Category 5 GxP-Critical systems get full lifecycle; Category 1 infrastructure gets streamlined IQ.\n**If fail:** If stakeholders push for reduced validation of critical systems, document the risk acceptance with QA sign-off.\n\n### Step 6: Design Governance Structure\n\nDefine the organisational framework for sustaining compliance:\n\n```markdown\n# Compliance Governance Structure\n\n## Roles and Responsibilities\n| Role | Responsibility | Authority |\n|------|---------------|-----------|\n| Quality Director | Overall compliance accountability | Approve validation strategies, accept risks |\n| System Owner | Day-to-day system compliance | Approve changes, ensure validated state |\n| Validation Lead | Plan and coordinate validation activities | Define validation scope and approach |\n| IT Operations | Technical infrastructure and security | Implement technical controls |\n| QA Reviewer | Independent review of validation deliverables | Accept or reject validation evidence |\n\n## Governance Committees\n| Committee | Frequency | Purpose | Members |\n|-----------|-----------|---------|---------|\n| Change Control Board | Weekly | Review and approve system changes | System owners, QA, IT, validation |\n| Periodic Review Committee | Quarterly | Review system compliance status | Quality director, system owners, QA |\n| Audit Programme Committee | Annual | Plan internal audit schedule | Quality director, lead auditor, QA |\n\n## Escalation Matrix\n| Issue | First Escalation | Second Escalation | Timeline |\n|-------|-----------------|-------------------|----------|\n| Critical audit finding | System Owner → QA Director | QA Director → Site Director | 24 hours |\n| Validated state breach | Validation Lead → System Owner | System Owner → Quality Director | 48 hours |\n| Data integrity incident | System Owner → QA Director | QA Director → Regulatory Affairs | 24 hours |\n```\n\n**Got:** Clear accountability for every compliance activity with no orphaned responsibilities.\n**If fail:** If roles overlap or are unassigned, convene a RACI workshop to resolve. Ambiguous ownership is a recurring regulatory citation.\n\n### Step 7: Compile the Compliance Architecture Document\n\nAssemble all components into the master document:\n\n```markdown\n# Compliance Architecture\n## Document ID: CA-[SITE]-[YYYY]-[NNN]\n## Version: 1.0\n\n### 1. Purpose and Scope\n[Organisation, site, product scope, regulatory scope]\n\n### 2. System Inventory\n[From Step 1]\n\n### 3. Criticality Classification\n[From Step 2]\n\n### 4. GAMP 5 Category Assignments\n[From Step 3]\n\n### 5. Regulatory Requirements Traceability\n[From Step 4]\n\n### 6. Validation Strategy\n[From Step 5]\n\n### 7. Governance Structure\n[From Step 6]\n\n### 8. Periodic Review Schedule\n- System inventory refresh: Annual\n- Criticality re-assessment: When new systems added or regulations change\n- Regulatory mapping update: When new guidance issued\n- Governance review: Annual or after organisational change\n\n### 9. Approval\n| Role | Name | Signature | Date |\n|------|------|-----------|------|\n| Quality Director | | | |\n| IT Director | | | |\n| Regulatory Affairs | | | |\n```\n\n**Got:** A single document that serves as the compliance blueprint for the entire regulated environment.\n**If fail:** If the document exceeds practical size, create a master document with references to subsidiary documents per system or domain.\n\n## Validation\n\n- [ ] System inventory includes every system that handles GxP data\n- [ ] Every system has a criticality tier with documented rationale\n- [ ] GAMP 5 categories assigned to all GxP-Critical and GxP-Supporting systems\n- [ ] Regulatory requirements traceability matrix covers all applicable clauses\n- [ ] Every GxP-Critical system has a defined validation strategy\n- [ ] Governance structure defines roles, committees, and escalation paths\n- [ ] All documents have unique IDs and version control\n- [ ] Compliance architecture document is approved by quality and IT leadership\n\n## Pitfalls\n\n- **Incomplete inventory**: Missing systems are invisible to compliance. Use network scans, software asset management tools, and department interviews — not asking IT.\n- **Binary thinking**: Systems are not \"GxP\" or \"not GxP.\" The three-tier model (Critical, Supporting, Non-GxP) avoids both over-validation and under-validation.\n- **Category confusion**: GAMP 5 category describes what the software IS, but validation effort should reflect how it is USED. A Category 4 system used for batch release needs more testing than a Category 4 system used for scheduling.\n- **Static architecture**: The compliance architecture is a living document. New systems, regulatory changes, and audit findings all require updates.\n- **Governance without teeth**: Committees that exist on paper but never meet provide no compliance value. Define meeting cadence and quorum requirements.\n\n## Related Skills\n\n- `perform-csv-assessment` — execute the validation strategy defined here for individual systems\n- `manage-change-control` — operationalise the change control process defined in governance\n- `implement-electronic-signatures` — implement e-signature controls mapped in the regulatory matrix\n- `prepare-inspection-readiness` — use this architecture as the foundation for inspection preparation\n- `conduct-gxp-audit` — audit against the compliance architecture as the baseline\n",{"name":5,"locale":23,"license":14,"metadata":24,"translator":31,"description":32,"allowed-tools":33,"source_commit":34,"source_locale":35,"translation_date":36},"caveman-lite",{"tags":25,"author":26,"domain":27,"version":28,"language":29,"complexity":30},"gxp, compliance, architecture, regulatory, gamp-5, governance","Philipp Thoss","compliance","1.0","multi","advanced","Julius Brussee homage — caveman","Design a compliance architecture that maps applicable regulations to computerized systems. Covers system inventory, criticality classification (GxP-critical, GxP-supporting, non-GxP), GAMP 5 category assignment, regulatory requirements traceability, and governance structure definition. Use when establishing a new regulated facility, formalising compliance across multiple systems, addressing a regulatory gap analysis, harmonising compliance after mergers or reorganisations, or preparing a site master file that references computerized systems.\n","Read Write Edit Bash Grep Glob","82c77053","en","2026-04-23","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fdesign-compliance-architecture",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add roohe\u002Fagentic-super-skills --skill design-compliance-architecture",{"tool":51,"command":52},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill design-compliance-architecture",{"tool":54,"command":55},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill design-compliance-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-compliance-architecture\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]