重要前提
安装AI Skills的关键前提是:必须科学上网,且开启TUN模式,这一点至关重要,直接决定安装能否顺利完成,在此郑重提醒三遍:科学上网,科学上网,科学上网。查看完整安装教程 →
qms-audit-expert by borghei/claude-skills
npx skills add https://github.com/borghei/claude-skills --skill qms-audit-expert医疗器械质量管理体系 ISO 13485 内部审核方法。
计划基于风险的内部审核方案:
| 风险等级 | 频率 | 标准 |
|---|---|---|
| 高 | 季度 | 设计控制、CAPA、生产验证 |
| 中 | 半年度 | 采购、培训、文件控制 |
| 低 | 年度 | 基础设施、管理评审(如果稳定) |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 条款 | 过程 | 关注领域 |
|---|---|---|
| 4.2 | 文件控制 | 文件批准、分发、作废控制 |
| 5.6 | 管理评审 | 输入完整、决策记录、行动跟踪 |
| 6.2 | 培训 | 能力定义、记录完整、有效性验证 |
| 7.3 | 设计控制 | 输入、评审、V&V、转移、变更 |
| 7.4 | 采购 | 供应商评价、来料检验 |
| 7.5 | 生产 | 作业指导书、过程验证、DHR |
| 7.6 | 校准 | 设备清单、校准状态、超差 |
| 8.2.2 | 内部审核 | 计划符合性、审核员独立性 |
| 8.3 | 不合格品 | 识别、隔离、处置 |
| 8.5 | CAPA | 根本原因、实施、有效性 |
在指派前验证审核员独立性:
执行系统化的内部审核:
| 方法 | 用于 | 文件记录 |
|---|---|---|
| 文件审查 | 程序、记录 | 文件编号、版本、日期 |
| 访谈 | 过程理解 | 受访者姓名、角色、摘要 |
| 观察 | 实际实践 | 观察到的内容、地点、时间 |
| 记录追溯 | 过程流程 | 记录 ID、日期、关联性 |
文件控制 (4.2):
设计控制 (7.3):
CAPA (8.5):
完整问题集请参见 references/iso13485-audit-guide.md。
使用以下格式记录每个发现:
Requirement: [具体的 ISO 13485 条款或程序]
Evidence: [观察、审查或听到的内容]
Gap: [证据如何未能满足要求]
示例:
Requirement: ISO 13485:2016 条款 7.6 要求在规定的间隔进行校准。
Evidence: pH 计 (EQ-042) 的校准记录显示上次校准日期为 2024-01-15。校准间隔为 12 个月。今天是 2025-03-20。
Gap: 设备校准已超期 2 个月,表明校准计划执行存在差距。
对审核发现进行分类和管理:
| 类别 | 定义 | 需要 CAPA | 时间线 |
|---|---|---|---|
| 严重 | 系统性失效或要素缺失 | 是 | 30 天 |
| 轻微 | 孤立性失误或部分实施 | 建议 | 60 天 |
| 观察项 | 改进机会 | 可选 | 酌情 |
Is required element absent or failed?
├── Yes → Systematic (multiple instances)? → MAJOR
│ └── No → Could affect product safety? → MAJOR
│ └── No → MINOR
└── No → Deviation from procedure?
├── Yes → Recurring? → MAJOR
│ └── No → MINOR
└── No → Improvement opportunity? → OBSERVATION
| 发现严重程度 | CAPA 深度 | 验证 |
|---|---|---|
| 严重 | 完整的根本原因分析 (5-Why, 鱼骨图) | 下次审核或 6 个月内 |
| 轻微 | 立即原因识别 | 下次计划审核 |
| 观察项 | 不需要 | 下次审核时记录 |
详细指南请参见 references/nonconformity-classification.md。
为认证机构或监管审核做准备:
文件:
人员:
设施:
references/iso13485-audit-guide.md 包含:
references/nonconformity-classification.md 包含:
# 生成优化的审核计划
python scripts/audit_schedule_optimizer.py --processes processes.json
# 交互模式
python scripts/audit_schedule_optimizer.py --interactive
# 用于集成的 JSON 输出
python scripts/audit_schedule_optimizer.py --processes processes.json --output json
生成基于风险的审核计划,考虑:
输出包括:
{
"processes": [
{
"name": "Design Control",
"iso_clause": "7.3",
"risk_level": "HIGH",
"last_audit_date": "2024-06-15",
"previous_findings": 2
},
{
"name": "Document Control",
"iso_clause": "4.2",
"risk_level": "MEDIUM",
"last_audit_date": "2024-09-01",
"previous_findings": 0
}
]
}
跟踪审核方案有效性:
| 指标 | 目标 | 测量方法 |
|---|---|---|
| 计划符合性 | >90% | 按时完成的审核 |
| 发现关闭率 | >95% | 在截止日期前关闭的发现 |
| 重复发现 | <10% | 连续审核中的相同发现 |
| CAPA 有效性 | >90% | 在后续跟进中验证有效 |
| 审核员利用率 | 4 天/月 | 每位合格审核员的审核天数 |
| 问题 | 可能原因 | 解决方案 |
|---|---|---|
| 计划优化器未为某个过程生成审核 | last_audit_date 较近且风险等级为低 | 低风险过程按年度计划。如果上次审核在 365 天内,则不会生成新审核。增加 risk_level 或 criticality_score 以触发更早的计划安排。 |
| 优化器将所有过程标记为超期 | processes.json 中的日期格式不正确 | 对 last_audit_date 使用 ISO 8601 格式 (YYYY-MM-DD)。无效日期会导致工具将上次审核视为缺失。 |
| 交互模式不接受输入 | 终端不支持 stdin 提示 | 使用基于文件的输入 --processes processes.json 代替 --interactive。 |
| 审核计划未覆盖所有 ISO 13485 条款 | 输入的过程列表不完整 | 优化器仅计划提供的过程。确保所有必需条款 (4.2, 5.6, 6.2, 7.3, 7.4, 7.5, 7.6, 8.2.2, 8.3, 8.5) 在输入中均有体现。 |
| 发现被分类为轻微但应为严重 | 分类应用不一致 | 应用决策树:系统性失效或要素缺失 = 严重;孤立性失误 = 轻微。考虑该发现是否可能影响产品安全(自动升级为严重)。 |
| 外部审核员提出内部已关闭的发现 | 在外部审核前未完成 CAPA 有效性验证 | 确保所有内部审核发现均在外部审核日期前完成 CAPA 并有记录的有效性验证。完成闭环,而不仅仅是完成行动。 |
| 过程负责人拒绝接受审核报告 | 发现缺乏客观证据支持 | 每个发现必须引用具体证据(文件编号、记录 ID、观察细节)。使用本技能中记录的"要求-证据-差距"格式重新处理发现。 |
范围内:
范围外:
| 技能 | 集成 |
|---|---|
| quality-manager-qms-iso13485 | 提供审核方案所评估的 QMS 过程框架;审核结果作为管理评审的输入 |
| capa-officer | 严重和轻微审核发现触发 CAPA 启动;CAPA 有效性验证关闭审核发现循环 |
| quality-documentation-manager | 文件控制审核覆盖(条款 4.2)验证文件编号、批准工作流和 Part 11 符合性 |
| quality-manager-qmr | 审核方案结果是必需的管理评审输入(条款 5.6.2);QMR 监督审核方案有效性 |
| risk-management-specialist | 风险管理过程审核(条款 7.1)验证 ISO 14971 实施和风险文件完整性 |
根据过程风险、发现历史和自上次审核以来的时间,生成基于风险的优化审核计划。
| 标志 | 必需 | 描述 |
|---|---|---|
--processes | 是(或 --interactive) | 包含过程定义的 JSON 文件路径,定义包括 name、iso_clause、risk_level (HIGH/MEDIUM/LOW)、last_audit_date、previous_findings 和 criticality_score |
--interactive | 否 | 启动交互模式进行引导式过程输入(文件输入的替代方案) |
--output | 否 | 输出格式:json 用于结构化输出,省略则为人类可读文本 |
每周安装次数
50
代码库
GitHub 星标
57
首次出现
2026年2月23日
安全审计
安装于
claude-code41
github-copilot36
gemini-cli36
codex36
cursor36
cline36
ISO 13485 internal audit methodology for medical device quality management systems.
Plan risk-based internal audit program:
| Risk Level | Frequency | Criteria |
|---|---|---|
| High | Quarterly | Design control, CAPA, production validation |
| Medium | Semi-annual | Purchasing, training, document control |
| Low | Annual | Infrastructure, management review (if stable) |
| Clause | Process | Focus Areas |
|---|---|---|
| 4.2 | Document Control | Document approval, distribution, obsolete control |
| 5.6 | Management Review | Inputs complete, decisions documented, actions tracked |
| 6.2 | Training | Competency defined, records complete, effectiveness verified |
| 7.3 | Design Control | Inputs, reviews, V&V, transfer, changes |
| 7.4 | Purchasing | Supplier evaluation, incoming inspection |
| 7.5 | Production | Work instructions, process validation, DHR |
| 7.6 | Calibration | Equipment list, calibration status, out-of-tolerance |
| 8.2.2 | Internal Audit | Schedule compliance, auditor independence |
| 8.3 | NC Product |
Verify auditor independence before assignment:
Conduct systematic internal audit:
| Method | Use For | Documentation |
|---|---|---|
| Document review | Procedures, records | Document number, version, date |
| Interview | Process understanding | Interviewee name, role, summary |
| Observation | Actual practice | What, where, when observed |
| Record trace | Process flow | Record IDs, dates, linkage |
Document Control (4.2):
Design Control (7.3):
CAPA (8.5):
See references/iso13485-audit-guide.md for complete question sets.
Document each finding with:
Requirement: [Specific ISO 13485 clause or procedure]
Evidence: [What was observed, reviewed, or heard]
Gap: [How evidence fails to meet requirement]
Example:
Requirement: ISO 13485:2016 Clause 7.6 requires calibration
at specified intervals.
Evidence: Calibration records for pH meter (EQ-042) show
last calibration 2024-01-15. Calibration interval is
12 months. Today is 2025-03-20.
Gap: Equipment is 2 months overdue for calibration,
representing a gap in calibration program execution.
Classify and manage audit findings:
| Category | Definition | CAPA Required | Timeline |
|---|---|---|---|
| Major | Systematic failure or absence of element | Yes | 30 days |
| Minor | Isolated lapse or partial implementation | Recommended | 60 days |
| Observation | Improvement opportunity | Optional | As appropriate |
Is required element absent or failed?
├── Yes → Systematic (multiple instances)? → MAJOR
│ └── No → Could affect product safety? → MAJOR
│ └── No → MINOR
└── No → Deviation from procedure?
├── Yes → Recurring? → MAJOR
│ └── No → MINOR
└── No → Improvement opportunity? → OBSERVATION
| Finding Severity | CAPA Depth | Verification |
|---|---|---|
| Major | Full root cause analysis (5-Why, Fishbone) | Next audit or within 6 months |
| Minor | Immediate cause identification | Next scheduled audit |
| Observation | Not required | Noted at next audit |
See references/nonconformity-classification.md for detailed guidance.
Prepare for certification body or regulatory audit:
Documentation:
Personnel:
Facility:
references/iso13485-audit-guide.md contains:
references/nonconformity-classification.md contains:
# Generate optimized audit schedule
python scripts/audit_schedule_optimizer.py --processes processes.json
# Interactive mode
python scripts/audit_schedule_optimizer.py --interactive
# JSON output for integration
python scripts/audit_schedule_optimizer.py --processes processes.json --output json
Generates risk-based audit schedule considering:
Output includes:
{
"processes": [
{
"name": "Design Control",
"iso_clause": "7.3",
"risk_level": "HIGH",
"last_audit_date": "2024-06-15",
"previous_findings": 2
},
{
"name": "Document Control",
"iso_clause": "4.2",
"risk_level": "MEDIUM",
"last_audit_date": "2024-09-01",
"previous_findings": 0
}
]
}
Track audit program effectiveness:
| Metric | Target | Measurement |
|---|---|---|
| Schedule compliance | >90% | Audits completed on time |
| Finding closure rate | >95% | Findings closed by due date |
| Repeat findings | <10% | Same finding in consecutive audits |
| CAPA effectiveness | >90% | Verified effective at follow-up |
| Auditor utilization | 4 days/month | Audit days per qualified auditor |
| Problem | Likely Cause | Resolution |
|---|---|---|
| Schedule optimizer produces no audits for a process | last_audit_date is recent and risk level is Low | Low-risk processes are scheduled annually. If the last audit was within 365 days, no new audit is generated. Increase risk_level or criticality_score to trigger earlier scheduling. |
| Optimizer flags all processes as overdue | Date format in processes.json is incorrect | Use ISO 8601 format (YYYY-MM-DD) for last_audit_date. Invalid dates cause the tool to treat the last audit as missing. |
| Interactive mode does not accept input |
In Scope:
Out of Scope:
| Skill | Integration |
|---|---|
| quality-manager-qms-iso13485 | Provides the QMS process framework that the audit program evaluates; audit results feed into management review inputs |
| capa-officer | Major and Minor audit findings trigger CAPA initiation; CAPA effectiveness verification closes the audit finding loop |
| quality-documentation-manager | Document control audit coverage (Clause 4.2) validates document numbering, approval workflows, and Part 11 compliance |
| quality-manager-qmr | Audit program results are a required management review input (Clause 5.6.2); QMR oversees audit program effectiveness |
| risk-management-specialist | Risk management process audit (Clause 7.1) verifies ISO 14971 implementation and risk file completeness |
Generates risk-based audit schedules optimized by process risk, findings history, and time since last audit.
| Flag | Required | Description |
|---|---|---|
--processes | Yes (or --interactive) | Path to JSON file containing process definitions with name, iso_clause, risk_level (HIGH/MEDIUM/LOW), last_audit_date, previous_findings, and criticality_score |
--interactive |
Weekly Installs
50
Repository
GitHub Stars
57
First Seen
Feb 23, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
claude-code41
github-copilot36
gemini-cli36
codex36
cursor36
cline36
多智能体结构化设计评审 - 智能体协作头脑风暴与设计验证流程
645 周安装
Claude提示词库 - 开发者必备的AI提示词模板集合,含代码审查、系统架构等角色扮演
295 周安装
Excel/XLSX文件编程操作指南:Python openpyxl/pandas与JavaScript xlsx库教程
295 周安装
uni-helper:AI驱动的uni-app开发工具集,Vite插件、TypeScript支持与脚手架
300 周安装
Vue JSON 渲染器:@json-render/vue - 动态生成 Vue 3 组件树
301 周安装
Three.js游戏开发指南 - WebGL 3D网页游戏制作教程与代码示例
297 周安装
营销活动执行指南:规划、跨渠道执行与效果分析全流程
299 周安装
| Identification, segregation, disposition |
| 8.5 | CAPA | Root cause, implementation, effectiveness |
| Terminal does not support stdin prompts |
Use file-based input with --processes processes.json instead of --interactive. |
| Audit schedule does not cover all ISO 13485 clauses | Input process list is incomplete | The optimizer schedules only the processes provided. Ensure all required clauses (4.2, 5.6, 6.2, 7.3, 7.4, 7.5, 7.6, 8.2.2, 8.3, 8.5) are represented in the input. |
| Finding classified as Minor but should be Major | Classification was applied inconsistently | Apply the decision tree: systematic failure or absent element = Major; isolated lapse = Minor. Consider whether the finding could affect product safety (auto-escalate to Major). |
| External auditor raises finding already closed internally | CAPA effectiveness verification not completed before external audit | Ensure all internal audit findings have completed CAPA with documented effectiveness verification before the external audit date. Close the loop, do not just complete the action. |
| Audit report rejected by process owner | Findings not supported by objective evidence | Every finding must reference specific evidence (document number, record ID, observation details). Rework findings using the Requirement-Evidence-Gap format documented in this skill. |
| No |
| Launch interactive mode for guided process entry (alternative to file input) |
--output | No | Output format: json for structured output, omit for human-readable text |