[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AS803YMWQHXSHAM1F6SMKA":3,"skill-same:01M7AS803YMWQHXSHAM1F6SMKA":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M7AS803YMWQHXSHAM1F6SMKA","capa-officer",null,"CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics. Use when running CAPA investigations, 5-Why analysis, fishbone diagrams, root cause determination, corrective action tracking, effectiveness verification, or CAPA program optimization.","GongYuanCaiJi\u002Fdsh-claude-skills","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7APPQ7AEZTDQB0N6HCPTR2X",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fcapa-officer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"capa-officer\"\ndescription: CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics. Use when running CAPA investigations, 5-Why analysis, fishbone diagrams, root cause determination, corrective action tracking, effectiveness verification, or CAPA program optimization.\ntriggers:\n  - CAPA investigation\n  - root cause analysis\n  - 5 Why analysis\n  - fishbone diagram\n  - corrective action\n  - preventive action\n  - effectiveness verification\n  - CAPA metrics\n  - nonconformance investigation\n  - quality issue investigation\n  - CAPA tracking\n  - audit finding CAPA\n---\n\n# CAPA Officer\n\nCorrective and Preventive Action (CAPA) management within Quality Management Systems, focusing on systematic root cause analysis, action implementation, and effectiveness verification.\n\n---\n\n## Table of Contents\n\n- [CAPA Investigation Workflow](#capa-investigation-workflow)\n- [Root Cause Analysis](#root-cause-analysis)\n- [Corrective Action Planning](#corrective-action-planning)\n- [Effectiveness Verification](#effectiveness-verification)\n- [CAPA Metrics and Reporting](#capa-metrics-and-reporting)\n- [Reference Documentation](#reference-documentation)\n- [Tools](#tools)\n\n---\n\n## CAPA Investigation Workflow\n\nConduct systematic CAPA investigation from initiation through closure:\n\n1. Document trigger event with objective evidence\n2. Assess significance and determine CAPA necessity\n3. Form investigation team with relevant expertise\n4. Collect data and evidence systematically\n5. Select and apply appropriate RCA methodology\n6. Identify root cause(s) with supporting evidence\n7. Develop corrective and preventive actions\n8. **Validation:** Root cause explains all symptoms; if eliminated, problem would not recur\n\n### CAPA Necessity Determination\n\n| Trigger Type | CAPA Required | Criteria |\n|--------------|---------------|----------|\n| Customer complaint (safety) | Yes | Any complaint involving patient\u002Fuser safety |\n| Customer complaint (quality) | Evaluate | Based on severity and frequency |\n| Internal audit finding (Major) | Yes | Systematic failure or absence of element |\n| Internal audit finding (Minor) | Recommended | Isolated lapse or partial implementation |\n| Nonconformance (recurring) | Yes | Same NC type occurring 3+ times |\n| Nonconformance (isolated) | Evaluate | Based on severity and risk |\n| External audit finding | Yes | All Major and Minor findings |\n| Trend analysis | Evaluate | Based on trend significance |\n\n### Investigation Team Composition\n\n| CAPA Severity | Required Team Members |\n|---------------|----------------------|\n| Critical | CAPA Officer, Process Owner, QA Manager, Subject Matter Expert, Management Rep |\n| Major | CAPA Officer, Process Owner, Subject Matter Expert |\n| Minor | CAPA Officer, Process Owner |\n\n### Evidence Collection Checklist\n\n- [ ] Problem description with specific details (what, where, when, who, how much)\n- [ ] Timeline of events leading to issue\n- [ ] Relevant records and documentation\n- [ ] Interview notes from involved personnel\n- [ ] Photos or physical evidence (if applicable)\n- [ ] Related complaints, NCs, or previous CAPAs\n- [ ] Process parameters and specifications\n\n---\n\n## Root Cause Analysis\n\nSelect and apply appropriate RCA methodology based on problem characteristics.\n\n### RCA Method Selection Decision Tree\n\n```\nIs the issue safety-critical or involves system reliability?\n├── Yes → Use FAULT TREE ANALYSIS\n└── No → Is human error the suspected primary cause?\n    ├── Yes → Use HUMAN FACTORS ANALYSIS\n    └── No → How many potential contributing factors?\n        ├── 1-2 factors (linear causation) → Use 5 WHY ANALYSIS\n        ├── 3-6 factors (complex, systemic) → Use FISHBONE DIAGRAM\n        └── Unknown\u002Fproactive assessment → Use FMEA\n```\n\n### 5 Why Analysis\n\nUse when: Single-cause issues with linear causation, process deviations with clear failure point.\n\n**Template:**\n\n```\nPROBLEM: [Clear, specific statement]\n\nWHY 1: Why did [problem] occur?\nBECAUSE: [First-level cause]\nEVIDENCE: [Supporting data]\n\nWHY 2: Why did [first-level cause] occur?\nBECAUSE: [Second-level cause]\nEVIDENCE: [Supporting data]\n\nWHY 3: Why did [second-level cause] occur?\nBECAUSE: [Third-level cause]\nEVIDENCE: [Supporting data]\n\nWHY 4: Why did [third-level cause] occur?\nBECAUSE: [Fourth-level cause]\nEVIDENCE: [Supporting data]\n\nWHY 5: Why did [fourth-level cause] occur?\nBECAUSE: [Root cause]\nEVIDENCE: [Supporting data]\n```\n\n**Example - Calibration Overdue:**\n\n```\nPROBLEM: pH meter (EQ-042) found 2 months overdue for calibration\n\nWHY 1: Why was calibration overdue?\nBECAUSE: Equipment was not on calibration schedule\nEVIDENCE: Calibration schedule reviewed, EQ-042 not listed\n\nWHY 2: Why was it not on the schedule?\nBECAUSE: Schedule not updated when equipment was purchased\nEVIDENCE: Purchase date 2023-06-15, schedule dated 2023-01-01\n\nWHY 3: Why was the schedule not updated?\nBECAUSE: No process requires schedule update at equipment purchase\nEVIDENCE: SOP-EQ-001 reviewed, no such requirement\n\nWHY 4: Why is there no such requirement?\nBECAUSE: Procedure written before equipment tracking was centralized\nEVIDENCE: SOP last revised 2019, equipment system implemented 2021\n\nWHY 5: Why has procedure not been updated?\nBECAUSE: Periodic review did not assess compatibility with new systems\nEVIDENCE: No review against new equipment system documented\n\nROOT CAUSE: Procedure review process does not assess compatibility\nwith organizational systems implemented after original procedure creation.\n```\n\n### Fishbone Diagram Categories (6M)\n\n| Category | Focus Areas | Typical Causes |\n|----------|-------------|----------------|\n| Man (People) | Training, competency, workload | Skill gaps, fatigue, communication |\n| Machine (Equipment) | Calibration, maintenance, age | Wear, malfunction, inadequate capacity |\n| Method (Process) | Procedures, work instructions | Unclear steps, missing controls |\n| Material | Specifications, suppliers, storage | Out-of-spec, degradation, contamination |\n| Measurement | Calibration, methods, interpretation | Instrument error, wrong method |\n| Mother Nature | Temperature, humidity, cleanliness | Environmental excursions |\n\nSee `references\u002Frca-methodologies.md` for complete method details and templates.\n\n### Root Cause Validation\n\nBefore proceeding to action planning, validate root cause:\n\n- [ ] Root cause can be verified with objective evidence\n- [ ] If root cause is eliminated, problem would not recur\n- [ ] Root cause is within organizational control\n- [ ] Root cause explains all observed symptoms\n- [ ] No other significant causes remain unaddressed\n\n---\n\n## Corrective Action Planning\n\nDevelop effective actions addressing identified root causes:\n\n1. Define immediate containment actions\n2. Develop corrective actions targeting root cause\n3. Identify preventive actions for similar processes\n4. Assign responsibilities and resources\n5. Establish timeline with milestones\n6. Define success criteria and verification method\n7. Document in CAPA action plan\n8. **Validation:** Actions directly address root cause; success criteria are measurable\n\n### Action Types\n\n| Type | Purpose | Timeline | Example |\n|------|---------|----------|---------|\n| Containment | Stop immediate impact | 24-72 hours | Quarantine affected product |\n| Correction | Fix the specific occurrence | 1-2 weeks | Rework or replace affected items |\n| Corrective | Eliminate root cause | 30-90 days | Revise procedure, add controls |\n| Preventive | Prevent in other areas | 60-120 days | Extend solution to similar processes |\n\n### Action Plan Components\n\n```\nACTION PLAN TEMPLATE\n\nCAPA Number: [CAPA-XXXX]\nRoot Cause: [Identified root cause]\n\nACTION 1: [Specific action description]\n- Type: [ ] Containment [ ] Correction [ ] Corrective [ ] Preventive\n- Responsible: [Name, Title]\n- Due Date: [YYYY-MM-DD]\n- Resources: [Required resources]\n- Success Criteria: [Measurable outcome]\n- Verification Method: [How success will be verified]\n\nACTION 2: [Specific action description]\n...\n\nIMPLEMENTATION TIMELINE:\nWeek 1: [Milestone]\nWeek 2: [Milestone]\nWeek 4: [Milestone]\nWeek 8: [Milestone]\n\nAPPROVAL:\nCAPA Owner: _____________ Date: _______\nProcess Owner: _____________ Date: _______\nQA Manager: _____________ Date: _______\n```\n\n### Action Effectiveness Indicators\n\n| Indicator | Target | Red Flag |\n|-----------|--------|----------|\n| Action scope | Addresses root cause completely | Treats only symptoms |\n| Specificity | Measurable deliverables | Vague commitments |\n| Timeline | Aggressive but achievable | No due dates or unrealistic |\n| Resources | Identified and allocated | Not specified |\n| Sustainability | Permanent solution | Temporary fix |\n\n---\n\n## Effectiveness Verification\n\nVerify corrective actions achieved intended results:\n\n1. Allow adequate implementation period (minimum 30-90 days)\n2. Collect post-implementation data\n3. Compare to pre-implementation baseline\n4. Evaluate against success criteria\n5. Verify no recurrence during verification period\n6. Document verification evidence\n7. Determine CAPA effectiveness\n8. **Validation:** All criteria met with objective evidence; no recurrence observed\n\n### Verification Timeline Guidelines\n\n| CAPA Severity | Wait Period | Verification Window |\n|---------------|-------------|---------------------|\n| Critical | 30 days | 30-90 days post-implementation |\n| Major | 60 days | 60-180 days post-implementation |\n| Minor | 90 days | 90-365 days post-implementation |\n\n### Verification Methods\n\n| Method | Use When | Evidence Required |\n|--------|----------|-------------------|\n| Data trend analysis | Quantifiable issues | Pre\u002Fpost comparison, trend charts |\n| Process audit | Procedure compliance issues | Audit checklist, interview notes |\n| Record review | Documentation issues | Sample records, compliance rate |\n| Testing\u002Finspection | Product quality issues | Test results, pass\u002Ffail data |\n| Interview\u002Fobservation | Training issues | Interview notes, observation records |\n\n### Effectiveness Determination\n\n```\nDid recurrence occur during verification period?\n├── Yes → CAPA INEFFECTIVE (re-investigate root cause)\n└── No → Were all effectiveness criteria met?\n    ├── Yes → CAPA EFFECTIVE (proceed to closure)\n    └── No → Extent of gap?\n        ├── Minor gap → Extend verification or accept with justification\n        └── Significant gap → CAPA INEFFECTIVE (revise actions)\n```\n\nSee `references\u002Feffectiveness-verification-guide.md` for detailed procedures.\n\n---\n\n## CAPA Metrics and Reporting\n\nMonitor CAPA program performance through key indicators.\n\n### Key Performance Indicators\n\n| Metric | Target | Calculation |\n|--------|--------|-------------|\n| CAPA cycle time | \u003C60 days average | (Close Date - Open Date) \u002F Number of CAPAs |\n| Overdue rate | \u003C10% | Overdue CAPAs \u002F Total Open CAPAs |\n| First-time effectiveness | >90% | Effective on first verification \u002F Total verified |\n| Recurrence rate | \u003C5% | Recurred issues \u002F Total closed CAPAs |\n| Investigation quality | 100% root cause validated | Root causes validated \u002F Total CAPAs |\n\n### Aging Analysis Categories\n\n| Age Bucket | Status | Action Required |\n|------------|--------|-----------------|\n| 0-30 days | On track | Monitor progress |\n| 31-60 days | Monitor | Review for delays |\n| 61-90 days | Warning | Escalate to management |\n| >90 days | Critical | Management intervention required |\n\n### Management Review Inputs\n\nMonthly CAPA status report includes:\n- Open CAPA count by severity and status\n- Overdue CAPA list with owners\n- Cycle time trends\n- Effectiveness rate trends\n- Source analysis (complaints, audits, NCs)\n- Recommendations for improvement\n\n---\n\n## Reference Documentation\n\n### Root Cause Analysis Methodologies\n\n`references\u002Frca-methodologies.md` contains:\n\n- Method selection decision tree\n- 5 Why analysis template and example\n- Fishbone diagram categories and template\n- Fault Tree Analysis for safety-critical issues\n- Human Factors Analysis for people-related causes\n- FMEA for proactive risk assessment\n- Hybrid approach guidance\n\n### Effectiveness Verification Guide\n\n`references\u002Feffectiveness-verification-guide.md` contains:\n\n- Verification planning requirements\n- Verification method selection\n- Effectiveness criteria definition (SMART)\n- Closure requirements by severity\n- Ineffective CAPA process\n- Documentation templates\n\n---\n\n## Tools\n\n### CAPA Tracker\n\n```bash\n# Generate CAPA status report\npython scripts\u002Fcapa_tracker.py --capas capas.json\n\n# Interactive mode for manual entry\npython scripts\u002Fcapa_tracker.py --interactive\n\n# JSON output for integration\npython scripts\u002Fcapa_tracker.py --capas capas.json --output json\n\n# Generate sample data file\npython scripts\u002Fcapa_tracker.py --sample > sample_capas.json\n```\n\nCalculates and reports:\n- Summary metrics (open, closed, overdue, cycle time, effectiveness)\n- Status distribution\n- Severity and source analysis\n- Aging report by time bucket\n- Overdue CAPA list\n- Actionable recommendations\n\n### Sample CAPA Input\n\n```json\n{\n  \"capas\": [\n    {\n      \"capa_number\": \"CAPA-2024-001\",\n      \"title\": \"Calibration overdue for pH meter\",\n      \"description\": \"pH meter EQ-042 found 2 months overdue\",\n      \"source\": \"AUDIT\",\n      \"severity\": \"MAJOR\",\n      \"status\": \"VERIFICATION\",\n      \"open_date\": \"2024-06-15\",\n      \"target_date\": \"2024-08-15\",\n      \"owner\": \"J. Smith\",\n      \"root_cause\": \"Procedure review gap\",\n      \"corrective_action\": \"Updated SOP-EQ-001\"\n    }\n  ]\n}\n```\n\n---\n\n## Regulatory Requirements\n\n### ISO 13485:2016 Clause 8.5\n\n| Sub-clause | Requirement | Key Activities |\n|------------|-------------|----------------|\n| 8.5.2 Corrective Action | Eliminate cause of nonconformity | NC review, cause determination, action evaluation, implementation, effectiveness review |\n| 8.5.3 Preventive Action | Eliminate potential nonconformity | Trend analysis, cause determination, action evaluation, implementation, effectiveness review |\n\n### FDA CAPA authority — ISO 13485 §8.5.2\u002F8.5.3 under the QMSR (legacy QSR 820.100, historical)\n\n> **⚠️ STATUS — QMSR transition (effective 2026-02-02):** FDA's Quality Management System Regulation (QMSR) final rule (89 FR 7496) amended 21 CFR Part 820 to **incorporate ISO 13485:2016 by reference** and removed the legacy QSR subsection structure. The CAPA section number **820.100 no longer exists in the CFR** — it is retained below only as a familiar index. The current FDA authority for CAPA is **ISO 13485:2016 §8.5.2 (corrective action) and §8.5.3 (preventive action)** (see clause table above), with complaint-handling additions in retained **21 CFR 820.35**. Cite the ISO 13485 clauses — not 820.100 — in current compliance documentation.\n\nCAPA elements required under ISO 13485 §8.5.2\u002F§8.5.3 (legacy QSR 820.100, historical):\n- Procedures for implementing corrective and preventive action\n- Analyzing quality data sources (complaints, NCs, audits, service records)\n- Investigating cause of nonconformities\n- Identifying actions needed to correct and prevent recurrence\n- Verifying actions are effective and do not adversely affect device\n- Submitting relevant information for management review\n\n### Common FDA 483 Observations\n\n| Observation | Root Cause Pattern |\n|-------------|-------------------|\n| CAPA not initiated for recurring issue | Trend analysis not performed |\n| Root cause analysis superficial | Inadequate investigation training |\n| Effectiveness not verified | No verification procedure |\n| Actions do not address root cause | Symptom treatment vs. cause elimination |\n\n> **Decision discipline:** The tools in this skill structure investigations and track CAPA status — they do not certify CAPA closure or compliance. CAPA effectiveness conclusions and closure decisions are yours to make and must be reviewed and signed off by the named CAPA owner and Quality function; route regulatory-classification questions (e.g., reportability, 21 CFR 803 MDR, recall under 21 CFR 806) to Regulatory Affairs.\n","# CAPA Officer\n\nCorrective and Preventive Action (CAPA) management within Quality Management Systems, focusing on systematic root cause analysis, action implementation, and effectiveness verification.\n\n---\n\n## Table of Contents\n\n- [CAPA Investigation Workflow](#capa-investigation-workflow)\n- [Root Cause Analysis](#root-cause-analysis)\n- [Corrective Action Planning](#corrective-action-planning)\n- [Effectiveness Verification](#effectiveness-verification)\n- [CAPA Metrics and Reporting](#capa-metrics-and-reporting)\n- [Reference Documentation](#reference-documentation)\n- [Tools](#tools)\n\n---\n\n## CAPA Investigation Workflow\n\nConduct systematic CAPA investigation from initiation through closure:\n\n1. Document trigger event with objective evidence\n2. Assess significance and determine CAPA necessity\n3. Form investigation team with relevant expertise\n4. Collect data and evidence systematically\n5. Select and apply appropriate RCA methodology\n6. Identify root cause(s) with supporting evidence\n7. Develop corrective and preventive actions\n8. **Validation:** Root cause explains all symptoms; if eliminated, problem would not recur\n\n### CAPA Necessity Determination\n\n| Trigger Type | CAPA Required | Criteria |\n|--------------|---------------|----------|\n| Customer complaint (safety) | Yes | Any complaint involving patient\u002Fuser safety |\n| Customer complaint (quality) | Evaluate | Based on severity and frequency |\n| Internal audit finding (Major) | Yes | Systematic failure or absence of element |\n| Internal audit finding (Minor) | Recommended | Isolated lapse or partial implementation |\n| Nonconformance (recurring) | Yes | Same NC type occurring 3+ times |\n| Nonconformance (isolated) | Evaluate | Based on severity and risk |\n| External audit finding | Yes | All Major and Minor findings |\n| Trend analysis | Evaluate | Based on trend significance |\n\n### Investigation Team Composition\n\n| CAPA Severity | Required Team Members |\n|---------------|----------------------|\n| Critical | CAPA Officer, Process Owner, QA Manager, Subject Matter Expert, Management Rep |\n| Major | CAPA Officer, Process Owner, Subject Matter Expert |\n| Minor | CAPA Officer, Process Owner |\n\n### Evidence Collection Checklist\n\n- [ ] Problem description with specific details (what, where, when, who, how much)\n- [ ] Timeline of events leading to issue\n- [ ] Relevant records and documentation\n- [ ] Interview notes from involved personnel\n- [ ] Photos or physical evidence (if applicable)\n- [ ] Related complaints, NCs, or previous CAPAs\n- [ ] Process parameters and specifications\n\n---\n\n## Root Cause Analysis\n\nSelect and apply appropriate RCA methodology based on problem characteristics.\n\n### RCA Method Selection Decision Tree\n\n```\nIs the issue safety-critical or involves system reliability?\n├── Yes → Use FAULT TREE ANALYSIS\n└── No → Is human error the suspected primary cause?\n    ├── Yes → Use HUMAN FACTORS ANALYSIS\n    └── No → How many potential contributing factors?\n        ├── 1-2 factors (linear causation) → Use 5 WHY ANALYSIS\n        ├── 3-6 factors (complex, systemic) → Use FISHBONE DIAGRAM\n        └── Unknown\u002Fproactive assessment → Use FMEA\n```\n\n### 5 Why Analysis\n\nUse when: Single-cause issues with linear causation, process deviations with clear failure point.\n\n**Template:**\n\n```\nPROBLEM: [Clear, specific statement]\n\nWHY 1: Why did [problem] occur?\nBECAUSE: [First-level cause]\nEVIDENCE: [Supporting data]\n\nWHY 2: Why did [first-level cause] occur?\nBECAUSE: [Second-level cause]\nEVIDENCE: [Supporting data]\n\nWHY 3: Why did [second-level cause] occur?\nBECAUSE: [Third-level cause]\nEVIDENCE: [Supporting data]\n\nWHY 4: Why did [third-level cause] occur?\nBECAUSE: [Fourth-level cause]\nEVIDENCE: [Supporting data]\n\nWHY 5: Why did [fourth-level cause] occur?\nBECAUSE: [Root cause]\nEVIDENCE: [Supporting data]\n```\n\n**Example - Calibration Overdue:**\n\n```\nPROBLEM: pH meter (EQ-042) found 2 months overdue for calibration\n\nWHY 1: Why was calibration overdue?\nBECAUSE: Equipment was not on calibration schedule\nEVIDENCE: Calibration schedule reviewed, EQ-042 not listed\n\nWHY 2: Why was it not on the schedule?\nBECAUSE: Schedule not updated when equipment was purchased\nEVIDENCE: Purchase date 2023-06-15, schedule dated 2023-01-01\n\nWHY 3: Why was the schedule not updated?\nBECAUSE: No process requires schedule update at equipment purchase\nEVIDENCE: SOP-EQ-001 reviewed, no such requirement\n\nWHY 4: Why is there no such requirement?\nBECAUSE: Procedure written before equipment tracking was centralized\nEVIDENCE: SOP last revised 2019, equipment system implemented 2021\n\nWHY 5: Why has procedure not been updated?\nBECAUSE: Periodic review did not assess compatibility with new systems\nEVIDENCE: No review against new equipment system documented\n\nROOT CAUSE: Procedure review process does not assess compatibility\nwith organizational systems implemented after original procedure creation.\n```\n\n### Fishbone Diagram Categories (6M)\n\n| Category | Focus Areas | Typical Causes |\n|----------|-------------|----------------|\n| Man (People) | Training, competency, workload | Skill gaps, fatigue, communication |\n| Machine (Equipment) | Calibration, maintenance, age | Wear, malfunction, inadequate capacity |\n| Method (Process) | Procedures, work instructions | Unclear steps, missing controls |\n| Material | Specifications, suppliers, storage | Out-of-spec, degradation, contamination |\n| Measurement | Calibration, methods, interpretation | Instrument error, wrong method |\n| Mother Nature | Temperature, humidity, cleanliness | Environmental excursions |\n\nSee `references\u002Frca-methodologies.md` for complete method details and templates.\n\n### Root Cause Validation\n\nBefore proceeding to action planning, validate root cause:\n\n- [ ] Root cause can be verified with objective evidence\n- [ ] If root cause is eliminated, problem would not recur\n- [ ] Root cause is within organizational control\n- [ ] Root cause explains all observed symptoms\n- [ ] No other significant causes remain unaddressed\n\n---\n\n## Corrective Action Planning\n\nDevelop effective actions addressing identified root causes:\n\n1. Define immediate containment actions\n2. Develop corrective actions targeting root cause\n3. Identify preventive actions for similar processes\n4. Assign responsibilities and resources\n5. Establish timeline with milestones\n6. Define success criteria and verification method\n7. Document in CAPA action plan\n8. **Validation:** Actions directly address root cause; success criteria are measurable\n\n### Action Types\n\n| Type | Purpose | Timeline | Example |\n|------|---------|----------|---------|\n| Containment | Stop immediate impact | 24-72 hours | Quarantine affected product |\n| Correction | Fix the specific occurrence | 1-2 weeks | Rework or replace affected items |\n| Corrective | Eliminate root cause | 30-90 days | Revise procedure, add controls |\n| Preventive | Prevent in other areas | 60-120 days | Extend solution to similar processes |\n\n### Action Plan Components\n\n```\nACTION PLAN TEMPLATE\n\nCAPA Number: [CAPA-XXXX]\nRoot Cause: [Identified root cause]\n\nACTION 1: [Specific action description]\n- Type: [ ] Containment [ ] Correction [ ] Corrective [ ] Preventive\n- Responsible: [Name, Title]\n- Due Date: [YYYY-MM-DD]\n- Resources: [Required resources]\n- Success Criteria: [Measurable outcome]\n- Verification Method: [How success will be verified]\n\nACTION 2: [Specific action description]\n...\n\nIMPLEMENTATION TIMELINE:\nWeek 1: [Milestone]\nWeek 2: [Milestone]\nWeek 4: [Milestone]\nWeek 8: [Milestone]\n\nAPPROVAL:\nCAPA Owner: _____________ Date: _______\nProcess Owner: _____________ Date: _______\nQA Manager: _____________ Date: _______\n```\n\n### Action Effectiveness Indicators\n\n| Indicator | Target | Red Flag |\n|-----------|--------|----------|\n| Action scope | Addresses root cause completely | Treats only symptoms |\n| Specificity | Measurable deliverables | Vague commitments |\n| Timeline | Aggressive but achievable | No due dates or unrealistic |\n| Resources | Identified and allocated | Not specified |\n| Sustainability | Permanent solution | Temporary fix |\n\n---\n\n## Effectiveness Verification\n\nVerify corrective actions achieved intended results:\n\n1. Allow adequate implementation period (minimum 30-90 days)\n2. Collect post-implementation data\n3. Compare to pre-implementation baseline\n4. Evaluate against success criteria\n5. Verify no recurrence during verification period\n6. Document verification evidence\n7. Determine CAPA effectiveness\n8. **Validation:** All criteria met with objective evidence; no recurrence observed\n\n### Verification Timeline Guidelines\n\n| CAPA Severity | Wait Period | Verification Window |\n|---------------|-------------|---------------------|\n| Critical | 30 days | 30-90 days post-implementation |\n| Major | 60 days | 60-180 days post-implementation |\n| Minor | 90 days | 90-365 days post-implementation |\n\n### Verification Methods\n\n| Method | Use When | Evidence Required |\n|--------|----------|-------------------|\n| Data trend analysis | Quantifiable issues | Pre\u002Fpost comparison, trend charts |\n| Process audit | Procedure compliance issues | Audit checklist, interview notes |\n| Record review | Documentation issues | Sample records, compliance rate |\n| Testing\u002Finspection | Product quality issues | Test results, pass\u002Ffail data |\n| Interview\u002Fobservation | Training issues | Interview notes, observation records |\n\n### Effectiveness Determination\n\n```\nDid recurrence occur during verification period?\n├── Yes → CAPA INEFFECTIVE (re-investigate root cause)\n└── No → Were all effectiveness criteria met?\n    ├── Yes → CAPA EFFECTIVE (proceed to closure)\n    └── No → Extent of gap?\n        ├── Minor gap → Extend verification or accept with justification\n        └── Significant gap → CAPA INEFFECTIVE (revise actions)\n```\n\nSee `references\u002Feffectiveness-verification-guide.md` for detailed procedures.\n\n---\n\n## CAPA Metrics and Reporting\n\nMonitor CAPA program performance through key indicators.\n\n### Key Performance Indicators\n\n| Metric | Target | Calculation |\n|--------|--------|-------------|\n| CAPA cycle time | \u003C60 days average | (Close Date - Open Date) \u002F Number of CAPAs |\n| Overdue rate | \u003C10% | Overdue CAPAs \u002F Total Open CAPAs |\n| First-time effectiveness | >90% | Effective on first verification \u002F Total verified |\n| Recurrence rate | \u003C5% | Recurred issues \u002F Total closed CAPAs |\n| Investigation quality | 100% root cause validated | Root causes validated \u002F Total CAPAs |\n\n### Aging Analysis Categories\n\n| Age Bucket | Status | Action Required |\n|------------|--------|-----------------|\n| 0-30 days | On track | Monitor progress |\n| 31-60 days | Monitor | Review for delays |\n| 61-90 days | Warning | Escalate to management |\n| >90 days | Critical | Management intervention required |\n\n### Management Review Inputs\n\nMonthly CAPA status report includes:\n- Open CAPA count by severity and status\n- Overdue CAPA list with owners\n- Cycle time trends\n- Effectiveness rate trends\n- Source analysis (complaints, audits, NCs)\n- Recommendations for improvement\n\n---\n\n## Reference Documentation\n\n### Root Cause Analysis Methodologies\n\n`references\u002Frca-methodologies.md` contains:\n\n- Method selection decision tree\n- 5 Why analysis template and example\n- Fishbone diagram categories and template\n- Fault Tree Analysis for safety-critical issues\n- Human Factors Analysis for people-related causes\n- FMEA for proactive risk assessment\n- Hybrid approach guidance\n\n### Effectiveness Verification Guide\n\n`references\u002Feffectiveness-verification-guide.md` contains:\n\n- Verification planning requirements\n- Verification method selection\n- Effectiveness criteria definition (SMART)\n- Closure requirements by severity\n- Ineffective CAPA process\n- Documentation templates\n\n---\n\n## Tools\n\n### CAPA Tracker\n\n```bash\n# Generate CAPA status report\npython scripts\u002Fcapa_tracker.py --capas capas.json\n\n# Interactive mode for manual entry\npython scripts\u002Fcapa_tracker.py --interactive\n\n# JSON output for integration\npython scripts\u002Fcapa_tracker.py --capas capas.json --output json\n\n# Generate sample data file\npython scripts\u002Fcapa_tracker.py --sample > sample_capas.json\n```\n\nCalculates and reports:\n- Summary metrics (open, closed, overdue, cycle time, effectiveness)\n- Status distribution\n- Severity and source analysis\n- Aging report by time bucket\n- Overdue CAPA list\n- Actionable recommendations\n\n### Sample CAPA Input\n\n```json\n{\n  \"capas\": [\n    {\n      \"capa_number\": \"CAPA-2024-001\",\n      \"title\": \"Calibration overdue for pH meter\",\n      \"description\": \"pH meter EQ-042 found 2 months overdue\",\n      \"source\": \"AUDIT\",\n      \"severity\": \"MAJOR\",\n      \"status\": \"VERIFICATION\",\n      \"open_date\": \"2024-06-15\",\n      \"target_date\": \"2024-08-15\",\n      \"owner\": \"J. Smith\",\n      \"root_cause\": \"Procedure review gap\",\n      \"corrective_action\": \"Updated SOP-EQ-001\"\n    }\n  ]\n}\n```\n\n---\n\n## Regulatory Requirements\n\n### ISO 13485:2016 Clause 8.5\n\n| Sub-clause | Requirement | Key Activities |\n|------------|-------------|----------------|\n| 8.5.2 Corrective Action | Eliminate cause of nonconformity | NC review, cause determination, action evaluation, implementation, effectiveness review |\n| 8.5.3 Preventive Action | Eliminate potential nonconformity | Trend analysis, cause determination, action evaluation, implementation, effectiveness review |\n\n### FDA CAPA authority — ISO 13485 §8.5.2\u002F8.5.3 under the QMSR (legacy QSR 820.100, historical)\n\n> **⚠️ STATUS — QMSR transition (effective 2026-02-02):** FDA's Quality Management System Regulation (QMSR) final rule (89 FR 7496) amended 21 CFR Part 820 to **incorporate ISO 13485:2016 by reference** and removed the legacy QSR subsection structure. The CAPA section number **820.100 no longer exists in the CFR** — it is retained below only as a familiar index. The current FDA authority for CAPA is **ISO 13485:2016 §8.5.2 (corrective action) and §8.5.3 (preventive action)** (see clause table above), with complaint-handling additions in retained **21 CFR 820.35**. Cite the ISO 13485 clauses — not 820.100 — in current compliance documentation.\n\nCAPA elements required under ISO 13485 §8.5.2\u002F§8.5.3 (legacy QSR 820.100, historical):\n- Procedures for implementing corrective and preventive action\n- Analyzing quality data sources (complaints, NCs, audits, service records)\n- Investigating cause of nonconformities\n- Identifying actions needed to correct and prevent recurrence\n- Verifying actions are effective and do not adversely affect device\n- Submitting relevant information for management review\n\n### Common FDA 483 Observations\n\n| Observation | Root Cause Pattern |\n|-------------|-------------------|\n| CAPA not initiated for recurring issue | Trend analysis not performed |\n| Root cause analysis superficial | Inadequate investigation training |\n| Effectiveness not verified | No verification procedure |\n| Actions do not address root cause | Symptom treatment vs. cause elimination |\n\n> **Decision discipline:** The tools in this skill structure investigations and track CAPA status — they do not certify CAPA closure or compliance. CAPA effectiveness conclusions and closure decisions are yours to make and must be reviewed and signed off by the named CAPA owner and Quality function; route regulatory-classification questions (e.g., reportability, 21 CFR 803 MDR, recall under 21 CFR 806) to Regulatory Affairs.\n",{"name":5,"triggers":24,"description":7},[25,26,27,28,29,30,31,32,33,34,35,36],"CAPA investigation","root cause analysis","5 Why analysis","fishbone diagram","corrective action","preventive action","effectiveness verification","CAPA metrics","nonconformance investigation","quality issue investigation","CAPA tracking","audit finding CAPA","main","992d25a425dee442a1f6a628d00a4fed33efe839","ra-qm-team\u002Fskills\u002Fcapa-officer","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 04:26:20",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill capa-officer",{"tool":50,"command":51},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill capa-officer",{"tool":53,"command":54},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill capa-officer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fcapa-officer\u002FSKILL.md",true,[58,64,68,74],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Feffectiveness-verification-guide.md","REFERENCE","参考文档",13611,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fcapa-officer\u002Freferences\u002Feffectiveness-verification-guide.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Frca-methodologies.md",15808,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fcapa-officer\u002Freferences\u002Frca-methodologies.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fcapa_tracker.py","SCRIPT","脚本",20986,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fcapa-officer\u002Fscripts\u002Fcapa_tracker.py",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Froot_cause_analyzer.py",17812,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fcapa-officer\u002Fscripts\u002Froot_cause_analyzer.py",[79,86,93,100,107,114],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7ASG5XZVP67CMMRENYFQWPW","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7ASFSGJF6G9KM40S1QJPR57","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7ASFFNCMS1X5X276VE277KW","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7ASF2BM8D9CDRQV1VBV7FV6","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7ASERRV1ES4S7QJRTTYWK0H","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7ASEANH3H547WQBZ7X8W5CX","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]