ra-qm-team/skills/regulatory-affairs-head/SKILL.md
Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017/745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.
npx skillsauth add alirezarezvani/claude-skills regulatory-affairs-headInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Regulatory strategy development, submission management, and global market access for medical device organizations.
Develop regulatory strategy aligned with business objectives and product characteristics.
| Factor | 510(k) | De Novo | PMA | |--------|--------|---------|-----| | Predicate Available | Yes | No | N/A | | Risk Level | Low-Moderate | Low-Moderate | High | | Clinical Data | Usually not required | May be required | Required | | Review Time | 90 days (MDUFA) | 150 days | 180 days | | User Fee | ~$22K (2024) | ~$135K | ~$440K | | Best For | Me-too devices | Novel low-risk | High-risk, novel |
REGULATORY STRATEGY
Product: [Name] Version: [X.X] Date: [Date]
1. PRODUCT OVERVIEW
Intended use: [One-sentence statement of intended patient population, body site, and clinical purpose]
Device classification: [Class I / II / III]
Technology: [Brief description, e.g., "AI-powered wound-imaging software, SaMD"]
2. TARGET MARKETS & TIMELINE
| Market | Pathway | Priority | Target Date |
|--------|----------------|----------|-------------|
| USA | 510(k) / PMA | 1 | Q1 20XX |
| EU | Class [X] MDR | 2 | Q2 20XX |
3. REGULATORY PATHWAY RATIONALE
FDA: [510(k) / De Novo / PMA] — Predicate: [K-number or "none"]
EU: Class [X] via [Annex IX / X / XI] — NB: [Name or TBD]
Rationale: [2–3 sentences on key factors driving pathway choice]
4. CLINICAL EVIDENCE STRATEGY
Requirements: [Summarize what each market needs, e.g., "510(k): bench + usability; EU Class IIb: PMCF study"]
Approach: [Literature review / Prospective study / Combination]
5. RISKS AND MITIGATION
| Risk | Prob | Impact | Mitigation |
|------------------------------|------|--------|-----------------------------------|
| Predicate delisted by FDA | Low | High | Identify secondary predicate now |
| NB audit backlog | Med | Med | Engage NB 6 months before target |
6. RESOURCE REQUIREMENTS
Budget: $[Amount] Personnel: [FTEs] External: [Consultants / CRO]
Prepare and submit FDA regulatory applications.
| Characteristic | Predicate (K213456) | Subject Device | Same? | Notes | |----------------|---------------------|----------------|-------|-------| | Intended use | Wound measurement | Wound measurement | ✓ | Identical | | Technology | 2D camera | 2D + AI analysis | ✗ | New TC; address below | | Energy type | Non-energized | Non-energized | ✓ | | | Patient contact | No | No | ✓ | | | SE conclusion | New TC does not raise new safety/effectiveness questions; bench data demonstrates equivalent accuracy (±2mm vs ±3mm predicate) |
| Milestone | 510(k) | De Novo | PMA | |-----------|--------|---------|-----| | Pre-Sub Meeting | Day -90 | Day -90 | Day -120 | | Submission | Day 0 | Day 0 | Day 0 | | RTA Review | Day 15 | Day 15 | Day 45 | | Substantive Review | Days 15–90 | Days 15–150 | Days 45–180 | | Decision | Day 90 | Day 150 | Day 180 |
| Category | Common Issues | Prevention | |----------|---------------|------------| | Substantial Equivalence | Weak predicate comparison; no performance data | Build SE table with data column; cite recognized standards | | Performance Testing | Incomplete protocols; missing worst-case rationale | Follow FDA-recognized standards; document worst-case justification | | Biocompatibility | Missing endpoints; no ISO 10993-1 risk assessment | Complete ISO 10993-1 matrix before testing | | Software | Inadequate hazard analysis; no cybersecurity bill of materials | IEC 62304 compliance + FDA cybersecurity guidance checklist | | Labeling | Inconsistent claims vs. IFU; missing symbols standard | Cross-check label against IFU; cite ISO 15223-1 for symbols |
See: references/fda-submission-guide.md
Achieve CE marking under EU MDR 2017/745.
| GSPR Ref | Requirement | Standard / Guidance | Evidence Document | Status | |----------|-------------|---------------------|-------------------|--------| | Annex I §1 | Safe design and manufacture | ISO 14971:2019 | Risk Management File v2.1 | Complete | | Annex I §11.1 | Devices with measuring function ±accuracy | EN ISO 15223-1 | Performance Test Report PT-003 | Complete | | Annex I §17 | Cybersecurity | MDCG 2019-16 | Cybersecurity Assessment CS-001 | In progress |
| Class | Clinical Requirement | Documentation | |-------|---------------------|---------------| | I | Clinical evaluation (CE) | CE report | | IIa | CE with literature focus | CE report + PMCF plan | | IIb | CE with clinical data | CE report + PMCF + clinical study (some) | | III | CE with clinical investigation | CE report + PMCF + clinical investigation |
See: references/eu-mdr-submission-guide.md
Coordinate regulatory approvals across international markets.
| Market | Size | Complexity | Recognition | Priority | |--------|------|------------|-------------|----------| | USA | Large | High | N/A | 1 | | EU | Large | High | N/A | 1–2 | | Canada | Medium | Medium | MDSAP | 2 | | Australia | Medium | Low | EU accepted | 2 | | Japan | Large | High | Local clinical | 3 | | China | Large | Very High | Local testing | 3 | | Brazil | Medium | High | GMP inspection | 3–4 |
| Document Type | Single Source | Localization Required | |---------------|---------------|----------------------| | Technical file core | Yes | Format adaptation | | Risk management | Yes | None | | Clinical data | Yes | Bridging assessment | | QMS certificate | Yes (ISO 13485) | Market-specific audit | | Labeling | Master label | Translation, local requirements | | IFU | Master content | Translation, local symbols |
See: references/global-regulatory-pathways.md
Monitor and respond to regulatory changes affecting product portfolio.
| Source | Type | Frequency | |--------|------|-----------| | FDA Federal Register | Regulations, guidance | Daily | | FDA Device Database | 510(k), PMA, recalls | Weekly | | EU Official Journal | MDR/IVDR updates | Weekly | | MDCG Guidance | EU implementation | As published | | ISO/IEC | Standards updates | Quarterly | | Notified Body | Audit findings, trends | Per interaction |
REGULATORY CHANGE IMPACT ASSESSMENT
Change: [Description] Source: [Regulation/Guidance]
Effective Date: [Date] Assessment Date: [Date] Assessed By: [Name]
AFFECTED PRODUCTS
| Product | Impact (H/M/L) | Action Required | Due Date |
|---------|----------------|------------------------|----------|
| [Name] | [H/M/L] | [Specific action] | [Date] |
COMPLIANCE ACTIONS
1. [Action] — Owner: [Name] — Due: [Date]
2. [Action] — Owner: [Name] — Due: [Date]
RESOURCE REQUIREMENTS: Budget $[X] | Personnel [X] hrs
APPROVAL: Regulatory _____________ Date _______ / Management _____________ Date _______
FDA Pathway Selection
Is predicate device available?
│
Yes─┴─No
│ │
▼ ▼
Is device Is risk level
substantially Low-Moderate?
equivalent? │
│ Yes─┴─No
Yes─┴─No │ │
│ │ ▼ ▼
▼ ▼ De Novo PMA
510(k) Consider required
De Novo
or PMA
EU MDR Classification
Is the device active?
│
Yes─┴─No
│ │
▼ ▼
Is it an Does it contact
implant? the body?
│ │
Yes─┴─No Yes─┴─No
│ │ │ │
▼ ▼ ▼ ▼
III IIb Check Class I
contact (measuring/
type sterile if
and applicable)
duration
| Factor | Schedule Pre-Sub | Skip Pre-Sub | |--------|------------------|--------------| | Novel Technology | ✓ | | | New Intended Use | ✓ | | | Complex Testing | ✓ | | | Uncertain Predicate | ✓ | | | Clinical Data Needed | ✓ | | | Well-established | | ✓ | | Clear Predicate | | ✓ | | Standard Testing | | ✓ |
| Situation | Escalation Level | Action | |-----------|------------------|--------| | Submission rejection | VP Regulatory | Root cause analysis, strategy revision | | Major deficiency | Director | Cross-functional response team | | Timeline at risk | Management | Resource reallocation review | | Regulatory change | VP Regulatory | Portfolio impact assessment | | Safety signal | Executive | Immediate containment and reporting |
| Tool | Purpose | Usage |
|------|---------|-------|
| regulatory_tracker.py | Track submission status and timelines | python regulatory_tracker.py |
Regulatory Tracker Features:
Example usage:
$ python regulatory_tracker.py --report status
Submission Status Report — 2024-11-01
┌──────────────────┬──────────┬────────────┬─────────────┬──────────┐
│ Product │ Market │ Type │ Target Date │ Status │
├──────────────────┼──────────┼────────────┼─────────────┼──────────┤
│ WoundScan Pro │ USA │ 510(k) │ 2024-12-01 │ On Track │
│ WoundScan Pro │ EU │ MDR IIb │ 2025-03-01 │ At Risk │
│ CardioMonitor X1 │ Canada │ Class II │ 2025-01-15 │ On Track │
└──────────────────┴──────────┴────────────┴─────────────┴──────────┘
1 submission at risk: WoundScan Pro EU — NB engagement not confirmed.
| Document | Content | |----------|---------| | fda-submission-guide.md | FDA pathways, requirements, review process | | eu-mdr-submission-guide.md | MDR classification, technical documentation, clinical evidence | | global-regulatory-pathways.md | Canada, Japan, China, Australia, Brazil requirements | | iso-regulatory-requirements.md | ISO 13485, 14971, 10993, IEC 62304, 62366 requirements |
| KPI | Target | Calculation | |-----|--------|-------------| | First-time approval rate | >85% | (Approved without major deficiency / Total submitted) × 100 | | On-time submission | >90% | (Submitted by target date / Total submissions) × 100 | | Review cycle compliance | >95% | (Responses within deadline / Total requests) × 100 | | Regulatory hold time | <20% | (Days on hold / Total review days) × 100 |
| Skill | Integration Point | |-------|-------------------| | mdr-745-specialist | Detailed EU MDR technical requirements | | fda-consultant-specialist | FDA submission deep expertise | | quality-manager-qms-iso13485 | QMS for regulatory compliance | | risk-management-specialist | ISO 14971 risk management |
data-ai
Use when you want to understand what Claude contributed vs what you drove in a session. Triggers on: /collab-proof, session retrospective, ai contribution analysis, collaboration evidence, what did claude do.
data-ai
Personal coach that teaches users to become Claude power users. Use this skill the FIRST time a user asks to "learn Claude", "be a power user", "coach me", "teach me Claude tricks", "what can Claude do", "make me better at prompting", or any variation. After activation, also use it on EVERY subsequent turn to detect missed optimization opportunities (vague prompts, ignored capabilities, manual work Claude could automate) and surface a single power-user tip. Trigger generously — most users do not know what they do not know, so err on the side of coaching.
development
Use when designing or revisiting product pricing — selecting a pricing model (subscription seat-based, usage-based, value-based, freemium, or hybrid), running Van Westendorp Price Sensitivity Meter analysis on WTP survey data, or designing Good/Better/Best packaging tiers. Recommends a model and a price range with trade-offs, never a single number. For Commercial leads, Product Marketing, and CMOs at the pricing-design moment — not deal-by-deal discounting, not brand positioning.
testing
Use when a startup is approached by a prospective partner and someone has to decide should we sign this partner, at what partner tier (referral / reseller / OEM / SI-consulting / strategic alliance), with what joint GTM commitment, and at what revshare. Classifies partner tier from independent-demand evidence vs. preferential-terms hunting, designs a 90-day joint GTM plan, models revshare against direct-sale margin, and surfaces kill criteria for unwinding under-performing partnerships. For Head of Partnerships, Head of BD, and Founder-CEOs doing reseller agreement, OEM deal, or strategic alliance review — not technical sale enablement, not channel cost economics, not M&A.