Token导航 LogoToken导航TokenDH.com
待分类只读github未标认证来源可访问许可证需确认审计通过

regulatory-affairs-head监管事务主管

Agent Skill

regulatory-affairs-head 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,088

周安装

87

GitHub Stars

103

下载量

696
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:regulatory-affairs-head(监管事务主管)
来源仓库:https://github.com/borghei/claude-skills
仓库路径:skills/regulatory-affairs-head
安装命令:
npx skills add https://github.com/borghei/claude-skills --skill regulatory-affairs-head
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill regulatory-affairs-head

简介

regulatory-affairs-head 协助医疗设备等产品的全球监管策略制定与申报管理。

  • 支持 FDA、欧盟 MDR 等法规识别与风险流程建立,确保产品合规上市。
  • 提供标准化工作流与模板,降低跨市场准入复杂度与时间成本。
  • 使用时需确认目标市场与产品分类,避免误用导致合规偏差。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Head of Regulatory Affairs

Regulatory strategy development, submission management, and global market access for medical device organizations.


Regulatory Strategy Workflow

The agent develops regulatory strategy aligned with business objectives and product characteristics.

Workflow: New Product Regulatory Strategy

  1. Gather product information -- collect intended use, device classification (risk level), technology platform, target markets, and timeline from stakeholders.
  2. Identify applicable regulations per target market:

- FDA (US): 21 CFR Part 820, 510(k)/PMA/De Novo - EU: MDR 2017/745, Notified Body requirements - Other markets: Health Canada, PMDA, NMPA, TGA

  1. Determine optimal regulatory pathway using the pathway selection matrix below -- compare submission types, assess predicate device availability, evaluate clinical evidence requirements.
  2. Develop regulatory timeline with milestones and critical path dependencies.
  3. Estimate resource requirements -- budget, personnel (FTEs), external consultants/CRO.
  4. Identify regulatory risks and define mitigation strategies for each.
  5. Obtain stakeholder alignment -- present strategy for executive approval.
  6. Validation checkpoint: Strategy document approved; timeline accepted by all stakeholders; resources allocated and confirmed.

Regulatory Pathway Selection Matrix

Factor510(k)De NovoPMA
Predicate AvailableYesNoN/A
Risk LevelLow-ModerateLow-ModerateHigh
Clinical DataUsually not requiredMay be requiredRequired
Review Time90 days (MDUFA)150 days180 days
User Fee~$22K (2024)~$135K~$440K
Best ForMe-too devicesNovel low-riskHigh-risk, novel

Example: Regulatory Strategy Output

REGULATORY STRATEGY

Product: CardioSense Wearable ECG Monitor
Version: 1.0
Date: 2026-03-12

1. PRODUCT OVERVIEW
   - Intended use: Continuous ECG monitoring for arrhythmia detection
   - Device classification: Class II (FDA), Class IIa (EU MDR)
   - Technology: Single-lead ECG with ML-based AF detection

2. TARGET MARKETS
   | Market | Priority | Timeline    |
   |--------|----------|-------------|
   | USA    | 1        | Q3 2026     |
   | EU     | 2        | Q1 2027     |
   | Canada | 3        | Q2 2027     |

3. REGULATORY PATHWAY
   - FDA: 510(k) — Predicate: AliveCor KardiaMobile (K142743)
   - EU: Class IIa via Annex IX (QMS) + Annex XI Part A (Product)
   - Rationale: Established predicate supports SE argument;
     MDR IIa classification per Rule 10 (active diagnostic)

4. CLINICAL EVIDENCE STRATEGY
   - Requirements: SE comparison + analytical performance data
   - Approach: Literature review for AF detection + bench study

5. RISKS AND MITIGATION
   | Risk                     | Probability | Impact | Mitigation                    |
   |--------------------------|-------------|--------|-------------------------------|
   | FDA requests clinical    | Medium      | High   | Pre-Sub meeting to align      |
   | NB capacity delay        | High        | Medium | Engage NB by Q4 2025         |
   | ML algorithm as SaMD     | Medium      | High   | Follow FDA AI/ML SaMD guidance|

FDA Submission Workflow

The agent prepares and submits FDA regulatory applications following established pathways.

Workflow: 510(k) Submission

  1. Confirm 510(k) pathway suitability -- verify predicate device identified, substantial equivalence supportable, no new intended use or technology concerns.
  2. Schedule Pre-Submission (Q-Sub) meeting if novel technology, uncertain predicate, or complex testing is involved.
  3. Compile submission package:

- Cover letter and administrative information - Device description and intended use - Substantial equivalence comparison - Performance testing data - Biocompatibility (if patient contact, per ISO 10993) - Software documentation (if applicable, per IEC 62304) - Labeling and IFU

  1. Conduct internal review -- quality check all sections against FDA checklist.
  2. Prepare eCopy per current FDA format requirements.
  3. Submit via FDA ESG portal with user fee payment.
  4. Monitor MDUFA clock and respond to AI/RTA requests within deadline.
  5. Validation checkpoint: Submission accepted (RTA complete); MDUFA goal date received; tracking system updated.

Workflow: PMA Submission

  1. Confirm PMA pathway -- Class III device or no suitable predicate; clinical data strategy defined.
  2. Complete IDE clinical study if required -- IDE approval, protocol execution, study report.
  3. Conduct Pre-Submission meeting with FDA.
  4. Compile PMA submission -- administrative/device information, manufacturing information, nonclinical studies, clinical studies, labeling.
  5. Submit original PMA application.
  6. Address FDA questions and deficiency letters within specified timeframes.
  7. Prepare for FDA facility inspection -- coordinate with Quality team.
  8. Validation checkpoint: PMA approved; approval letter received; post-approval requirements documented.

FDA Submission Timeline

Milestone510(k)De NovoPMA
Pre-Sub MeetingDay -90Day -90Day -120
SubmissionDay 0Day 0Day 0
RTA ReviewDay 15Day 15Day 45
Substantive ReviewDays 15-90Days 15-150Days 45-180
DecisionDay 90Day 150Day 180

Common FDA Deficiencies

CategoryCommon IssuesPrevention
Substantial EquivalenceWeak predicate comparisonStrong SE argument upfront
Performance TestingIncomplete test protocolsFollow recognized standards
BiocompatibilityMissing endpointsISO 10993 risk assessment
SoftwareInadequate documentationIEC 62304 compliance
LabelingInconsistent claimsEarly labeling review

See: references/fda-submission-guide.md


EU MDR Submission Workflow

The agent achieves CE marking under EU MDR 2017/745.

Workflow: MDR Technical Documentation

  1. Confirm device classification per MDR Annex VIII rules.
  2. Select conformity assessment route based on class:

- Class I: Self-declaration - Class IIa/IIb: Notified Body involvement - Class III: Full NB assessment

  1. Select and engage Notified Body (for Class IIa+) -- evaluate scope, capacity, experience, and timeline.
  2. Compile Technical Documentation per Annex II:

- Device description and specifications - Design and manufacturing information - GSPR checklist (General Safety and Performance Requirements) - Benefit-risk analysis and risk management (ISO 14971) - Clinical evaluation per Annex XIV - Post-market surveillance plan

  1. Establish and document QMS per ISO 13485.
  2. Submit application to Notified Body.
  3. Address NB questions and coordinate audit logistics.
  4. Validation checkpoint: CE certificate issued; Declaration of Conformity signed; EUDAMED registration complete.

Clinical Evidence Requirements by Class

ClassClinical RequirementDocumentation
IClinical evaluation (CE)CE report
IIaCE with literature focusCE report + PMCF plan
IIbCE with clinical dataCE report + PMCF + clinical study (some)
IIICE with clinical investigationCE report + PMCF + clinical investigation

Notified Body Selection Criteria

CriterionConsideration
ScopeDevice category expertise
CapacityAvailability and review timeline
ExperienceTrack record in your technology
GeographyProximity for audits
CostFee structure transparency
CommunicationResponsiveness and clarity

See: references/eu-mdr-submission-guide.md


Global Market Access Workflow

The agent coordinates regulatory approvals across international markets.

Workflow: Multi-Market Submission Strategy

  1. Define target markets based on business priorities and revenue projections.
  2. Sequence markets for efficient evidence leverage:

- Phase 1: FDA + EU (reference markets) - Phase 2: Recognition markets (Canada via MDSAP, Australia via TGA) - Phase 3: Major markets (Japan PMDA, China NMPA) - Phase 4: Emerging markets

  1. Identify local requirements per market -- clinical data acceptability, local agent/representative needs, language and labeling requirements.
  2. Develop master technical file with localization plan.
  3. Establish in-country regulatory support.
  4. Execute parallel or sequential submissions per sequencing strategy.
  5. Track approvals and coordinate product launches.
  6. Validation checkpoint: All target market approvals obtained; registration database updated; launch dates confirmed.

Market Priority Matrix

MarketSizeComplexityRecognitionPriority
USALargeHighN/A1
EULargeHighN/A1-2
CanadaMediumMediumMDSAP2
AustraliaMediumLowEU accepted2
JapanLargeHighLocal clinical3
ChinaLargeVery HighLocal testing3
BrazilMediumHighGMP inspection3-4

See: references/global-regulatory-pathways.md


Regulatory Intelligence Workflow

The agent monitors and responds to regulatory changes affecting the product portfolio.

Workflow: Regulatory Change Management

  1. Monitor regulatory sources -- FDA Federal Register, EU Official Journal, MDCG guidance, Notified Body communications, industry associations (AdvaMed, MedTech Europe).
  2. Assess relevance to current product portfolio and pipeline.
  3. Evaluate impact -- timeline to compliance, resource requirements, product changes needed.
  4. Develop compliance action plan with owners and deadlines.
  5. Communicate to affected stakeholders across functions.
  6. Implement required changes within established timelines.
  7. Document compliance status for management review and audit readiness.
  8. Validation checkpoint: Compliance action plan approved; changes implemented on schedule; no gaps at next audit.

Regulatory Monitoring Sources

SourceTypeFrequency
FDA Federal RegisterRegulations, guidanceDaily
FDA Device Database510(k), PMA, recallsWeekly
EU Official JournalMDR/IVDR updatesWeekly
MDCG GuidanceEU implementationAs published
ISO/IECStandards updatesQuarterly
Notified BodyAudit findings, trendsPer interaction

Decision Frameworks

Pathway Selection Decision Tree

Is predicate device available?
            |
        Yes-+-No
         |     |
         v     v
    Is device   Is risk level
    substantially  Low-Moderate?
    equivalent?       |
         |        Yes-+-No
     Yes-+-No      |     |
      |     |      v     v
      v     v   De Novo  PMA
    510(k)  Consider      required
           De Novo
           or PMA

Pre-Submission Meeting Decision

FactorSchedule Pre-SubSkip Pre-Sub
Novel TechnologyYes
New Intended UseYes
Complex TestingYes
Uncertain PredicateYes
Clinical Data NeededYes
Well-establishedYes
Clear PredicateYes
Standard TestingYes

Regulatory Escalation Criteria

SituationEscalation LevelAction
Submission rejectionVP RegulatoryRoot cause analysis, strategy revision
Major deficiencyDirectorCross-functional response team
Timeline at riskManagementResource reallocation review
Regulatory changeVP RegulatoryPortfolio impact assessment
Safety signalExecutiveImmediate containment and reporting

Tools and References

Scripts

ToolPurposeUsage
regulatory_tracker.pyTrack submission status and timelinespython regulatory_tracker.py --help
# Example: Track active submissions
python scripts/regulatory_tracker.py --status active --format markdown

# Example: Check overdue submissions
python scripts/regulatory_tracker.py --overdue --notify

References

DocumentContent
fda-submission-guide.mdFDA pathways, requirements, review process
eu-mdr-submission-guide.mdMDR classification, technical documentation, clinical evidence
global-regulatory-pathways.mdCanada, Japan, China, Australia, Brazil requirements
iso-regulatory-requirements.mdISO 13485, 14971, 10993, IEC 62304, 62366 requirements

Key Performance Indicators

KPITargetCalculation
First-time approval rate>85%(Approved without major deficiency / Total submitted) x 100
On-time submission>90%(Submitted by target date / Total submissions) x 100
Review cycle compliance>95%(Responses within deadline / Total requests) x 100
Regulatory hold time<20%(Days on hold / Total review days) x 100

Related Skills

SkillIntegration Point
mdr-745-specialistDetailed EU MDR technical requirements
fda-consultant-specialistFDA submission deep expertise
quality-manager-qms-iso13485QMS for regulatory compliance
risk-management-specialistISO 14971 risk management

Troubleshooting

ProblemLikely CauseResolution
Regulatory tracker shows "No existing data file found"Data file does not exist at the expected pathCreate an initial submissions JSON file or use the tracker to add a first submission. The tool creates the file on first save.
Submission status shows as PLANNING when it should be SUBMITTEDStatus not updated after submissionUpdate the submission record with submission_status: SUBMITTED and submission_date. The tracker does not auto-detect FDA ESG submission status.
Overdue notification fires for approved submissionactual_approval_date field not populatedUpdate the record with the actual approval date. The tracker compares target_approval_date against today when actual_approval_date is null.
510(k) pathway selected but clinical data still neededNovel technology or uncertain predicateSchedule a Pre-Submission (Q-Sub) meeting with FDA. Novel technologies or complex testing may require clinical evidence even under the 510(k) pathway.
Notified Body timeline exceeds planNB capacity constraints (common in 2025-2026)Engage the NB as early as possible (6+ months before target submission). The number of designated MDR NBs has grown to ~50 as of 2024, but capacity remains tight for complex device classes.
EUDAMED registration blockedEUDAMED modules not yet mandatory or data upload issuesDevelop a secure process for uploading device data into EUDAMED. Certain modules become mandatory in 2026. Prepare data structures proactively.
Multi-market submission timeline keeps slippingSequential submissions creating cascading delaysWhere possible, shift to parallel submission strategy. Use FDA + EU as reference markets and leverage MDSAP for recognition markets (Canada, Australia, Japan, Brazil).

Success Criteria

  • First-time regulatory approval rate exceeds 85% across all submission types (510(k), PMA, De Novo, CE marking)
  • Regulatory submission timelines met for 90%+ of submissions (submitted by target date)
  • Pre-Submission meetings scheduled and completed for all novel technology, uncertain predicate, or complex testing submissions
  • FDA review cycle compliance exceeds 95% (responses to AI/RTA/deficiency requests submitted within deadline)
  • EU MDR Technical Documentation complete and accepted by Notified Body with no critical findings on first review
  • Global market access strategy documented with phased market sequencing, resource estimates, and risk mitigation for each target jurisdiction
  • Regulatory intelligence monitoring active for all applicable jurisdictions with change assessments completed within 30 days of publication

Scope & Limitations

In Scope:

  • Regulatory strategy development for medical devices across FDA, EU MDR, and global markets
  • FDA submission management (510(k), PMA, De Novo, Q-Sub/Pre-Submission)
  • EU MDR conformity assessment route selection and Notified Body engagement
  • Global market access planning and multi-market submission sequencing
  • Regulatory intelligence monitoring and change management
  • Submission timeline planning and milestone tracking
  • Regulatory pathway selection decision frameworks

Out of Scope:

  • Clinical trial design, execution, or data analysis (the skill addresses clinical evidence strategy but not clinical operations)
  • Detailed technical file content creation (use mdr-745-specialist for GSPR checklists, Annex II documentation)
  • Quality system management (use quality-manager-qms-iso13485 for QMS processes)
  • Post-market surveillance program execution (the skill defines PMS strategy but execution is managed by PMS teams)
  • Reimbursement strategy or health technology assessment (HTA) submissions
  • Patent or intellectual property strategy related to regulatory pathways
  • In vitro diagnostic (IVD) specific regulatory requirements under IVDR 2017/746

Integration Points

SkillIntegration
mdr-745-specialistDetailed EU MDR technical requirements, GSPR checklists, Annex VIII classification rules, and EUDAMED registration
fda-consultant-specialistFDA submission deep expertise including QMSR alignment, HIPAA, cybersecurity guidance, and 510(k)/PMA specifics
quality-manager-qms-iso13485QMS certification is a prerequisite for MDR conformity assessment and supports FDA QMSR compliance
risk-management-specialistISO 14971 risk management file is required for both FDA submissions and EU MDR Technical Documentation
quality-manager-qmrRegulatory changes affecting the QMS are management review inputs; QMR coordinates compliance across jurisdictions

Tool Reference

regulatory_tracker.py

Tracks regulatory submission status, timelines, and overdue notifications across all markets.

FlagRequiredDescription
--statusNoFilter submissions by status: active, planning, submitted, approved, all
--overdueNoShow only submissions past their target approval date without an actual approval date
--notifyNoGenerate notification alerts for overdue or at-risk submissions
--formatNoOutput format: markdown for formatted text, omit for default display

Note: The tracker operates on a regulatory_submissions.json data file (default path). Submissions are added and updated programmatically through the RegulatoryTracker class API. The tool supports submission types: FDA_510K, FDA_PMA, FDA_DE_NOVO, EU_MDR_CE, ISO_CERTIFICATION, GLOBAL_REGULATORY.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.39%
按下载量换算232

Claude

29.76%
按下载量换算207

Cursor

19.57%
按下载量换算136

Gemini CLI

9.09%
按下载量换算63

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills