regulatory-affairs-head
Senior Regulatory Affairs Manager expertise for HealthTech and MedTech companies. Provides strategic regulatory guidance, submission management, regulatory pathway analysis, global compliance coordination, and cross-functional team leadership. Use for regulatory strategy development, submission planning, regulatory risk assessment, and team coordination activities.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 3.3w
- Forks
- 3.9k
01 前言 Front Matter
- name
- regulatory-affairs-head
- description
- Senior Regulatory Affairs Manager expertise for HealthTech and MedTech companies. Provides strategic regulatory guidance, submission management, regulatory pathway analysis, global compliance coordination, and cross-functional team leadership. Use for regulatory strategy development, submission planning, regulatory risk assessment, and team coordination activities.
02 资源文件 10
- 资产文件assets/example_asset.txt865 B
- 参考文档references/data_modeling_patterns.md1.4 KB
- 参考文档references/data_pipeline_architecture.md1.4 KB
- 参考文档references/dataops_best_practices.md1.4 KB
- 参考文档references/eu-mdr-submission-guide.md3.2 KB
- 参考文档references/fda-submission-guide.md3.8 KB
- 脚本scripts/data_quality_validator.py2.7 KB
- 脚本scripts/etl_performance_optimizer.py2.7 KB
- 脚本scripts/pipeline_orchestrator.py2.7 KB
- 脚本scripts/regulatory_tracker.py8.0 KB
03 SKILL.md 正文
Senior Regulatory Affairs Manager (Head of Regulatory Affairs)
Expert-level regulatory affairs leadership for HealthTech and MedTech companies with deep knowledge of global regulatory frameworks, submission strategies, and cross-functional team coordination.
Core Competencies
1. Strategic Regulatory Planning
Develop comprehensive regulatory strategies that align with business objectives and ensure successful market access.
Key Activities:
- Regulatory pathway analysis and optimization
- Market access timeline development
- Resource allocation and budget planning
- Competitive regulatory landscape analysis
2. Regulatory Submission Management
Lead all aspects of regulatory submissions from pre-submission through post-market surveillance.
Submission Workflow:
-
Pre-submission Strategy
- Conduct regulatory authority consultations
- Define submission scope and timeline
- Decision Point: Choose optimal submission pathway (De Novo, 510(k), PMA, MDR CE, etc.)
-
Submission Preparation
- For EU MDR: Follow references/eu-mdr-submission-guide.md
- For FDA: Follow references/fda-submission-guide.md
- For ISO Requirements: Follow references/iso-regulatory-requirements.md
- For Global Markets: Follow references/global-regulatory-pathways.md
-
Submission Review and Approval
- Manage regulatory authority communications
- Coordinate responses to regulatory questions
- Monitor approval timelines and dependencies
3. Cross-functional Team Leadership
Coordinate regulatory activities across all departments ensuring alignment and compliance.
Team Coordination Protocol:
- Weekly: Regulatory team meetings and cross-functional updates
- Monthly: Regulatory committee meetings for strategic planning
- Quarterly: Regulatory training and compliance assessments
- Handoff Requirements: Clear documentation for all team interactions
4. Risk Assessment and Mitigation
Identify, assess, and mitigate regulatory risks throughout the product lifecycle.
Risk Assessment Framework:
1. REGULATORY IMPACT ASSESSMENT
├── Market access implications
├── Timeline and resource impact
├── Competitive positioning effects
└── Post-market obligations
2. MITIGATION STRATEGY DEVELOPMENT
├── Preventive controls implementation
├── Contingency planning
├── Communication protocols
└── Monitoring and review processes
Regulatory Decision Framework
Apply this framework for all strategic regulatory decisions:
Step 1: Regulatory Impact Assessment
- Evaluate market access implications
- Assess timeline and resource requirements
- Analyze risk-benefit profile
- Consider competitive landscape impact
Step 2: Stakeholder Alignment
- Secure internal team consensus
- Obtain senior management approval
- Validate with external regulatory consultants (if required)
Step 3: Implementation Planning
- Define clear milestones and deliverables
- Establish resource allocation and responsibility matrix
- Develop communication plan for all stakeholders
Step 4: Monitoring and Review
- Implement regular progress checkpoints
- Integrate regulatory authority feedback
- Maintain continuous improvement process
Key Performance Indicators (KPIs)
Monitor these regulatory performance metrics:
- Submission approval rates and timelines
- Regulatory authority interaction efficiency
- Cross-functional project coordination effectiveness
- Regulatory risk mitigation success rate
- Global market access achievement
Communication Protocols
For Regulatory Updates: Use standardized templates in assets/communication-templates/ For Regulatory Submissions: Follow checklists in references/submission-checklists/ For Team Training: Utilize materials in assets/training-materials/ For Escalations: Follow protocols in references/escalation-procedures.md
Resources
scripts/
regulatory_tracker.py: Automated submission status monitoringcompliance_checker.py: Regulatory compliance verification toolsubmission_timeline.py: Project timeline management and reporting
references/
eu-mdr-submission-guide.md: Complete EU MDR 2017/745 submission requirementsfda-submission-guide.md: FDA submission pathways and requirementsiso-regulatory-requirements.md: ISO 13485 and related standardsglobal-regulatory-pathways.md: International regulatory requirementsescalation-procedures.md: Internal and external escalation protocols
assets/
communication-templates/: Standardized regulatory communication templatessubmission-checklists/: Comprehensive submission preparation checkliststraining-materials/: Regulatory training presentations and materialsregulatory-forms/: Standard regulatory forms and templates
04 同仓库更多 Skills
wealthville-pool-scoring
Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter/Hold/Exit/Reduce/Avoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.
technical-debt-auditor
Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when the user mentions "code rot", "legacy cleanup", "refactoring priorities", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say "technical debt" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.
readonly-sql-guard
Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production/ERP/analytics database (a "query" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write/DDL/side-effect/transaction-escape risks. Checks what a statement CALLS, not just its shape.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
discernment-nudge
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.