
Regulatory Affairs Head
- 43 installs
- 51 repo stars
- Updated November 25, 2025
- ovachiever/droid-tings
Helps with ai & agent building tasks during AI-assisted development.
About
regulatory-affairs-head is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.
- regulatory-affairs-head
- AI & Agent Building
- AI-coding skill
Regulatory Affairs Head by the numbers
- 43 all-time installs (skills.sh)
- Ranked #7,884 of 16,556 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Jul 27, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ovachiever/droid-tings --skill regulatory-affairs-headAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 43 |
|---|---|
| repo stars | ★ 51 |
| Last updated | November 25, 2025 |
| Repository | ovachiever/droid-tings ↗ |
What it does
Helps with ai & agent building tasks during AI-assisted development.
Files
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: 1. 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.)
2. 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
3. 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 processesRegulatory 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
# Example Asset File
This placeholder represents where asset files would be stored.
Replace with actual asset files (templates, images, fonts, etc.) or delete if not needed.
Asset files are NOT intended to be loaded into context, but rather used within
the output Claude produces.
Example asset files from other skills:
- Brand guidelines: logo.png, slides_template.pptx
- Frontend builder: hello-world/ directory with HTML/React boilerplate
- Typography: custom-font.ttf, font-family.woff2
- Data: sample_data.csv, test_dataset.json
## Common Asset Types
- Templates: .pptx, .docx, boilerplate directories
- Images: .png, .jpg, .svg, .gif
- Fonts: .ttf, .otf, .woff, .woff2
- Boilerplate code: Project directories, starter files
- Icons: .ico, .svg
- Data files: .csv, .json, .xml, .yaml
Note: This is a text placeholder. Actual assets can be any file type.
EU MDR 2017/745 Submission Guide
MDR Classification and Conformity Assessment Routes
Class I Devices
- Self-certification under Annex II
- Technical documentation requirements per Annex II
- Declaration of Conformity mandatory
- UDI registration required
Class IIa Devices
- Notified Body involvement for Annex III Module C2 + Annex V
- Quality management system assessment
- Technical documentation review
- Ongoing surveillance requirements
Class IIb Devices
- Notified Body certification under Annex III Module B + C or D
- Type examination or Full quality assurance route
- Design examination requirements
- Production surveillance obligations
Class III Devices
- Comprehensive Notified Body assessment
- Type examination + production surveillance OR
- Full quality assurance system approach
- Design dossier requirements per Annex II
Key MDR Submission Requirements
1. Technical Documentation (Annex II)
- Device description and intended purpose
- Risk management documentation (ISO 14971)
- Clinical evidence per Annex XIV
- Post-market surveillance plan
- Performance evaluation reports
2. Quality Management System (Annex I, Chapter II)
- ISO 13485 compliant QMS
- Design controls implementation
- Risk management integration
- Clinical evaluation procedures
- Post-market surveillance system
3. Clinical Evidence Requirements
- Clinical evaluation plan per Annex XIV
- Literature review and gap analysis
- Clinical investigation if required
- Post-market clinical follow-up plan
- Clinical evaluation report updating
4. UDI System Implementation
- UDI-DI assignment and registration
- UDI-PI requirements for higher risk devices
- EUDAMED registration obligations
- Labeling compliance with UDI requirements
Submission Timeline Framework
Pre-Submission Phase (6-12 months)
1. Gap analysis against MDR requirements 2. Classification confirmation with regulatory experts 3. Notified Body selection and preliminary discussions 4. Clinical evidence strategy development 5. UDI strategy and EUDAMED preparation
Submission Preparation (3-6 months)
1. Technical documentation compilation 2. QMS documentation review and update 3. Clinical evaluation completion 4. Risk management file finalization 5. Notified Body application submission
Review and Certification (6-18 months)
1. Initial assessment by Notified Body 2. Questions and clarifications response 3. Audit activities coordination 4. Certificate issuance and market access 5. Post-market obligations activation
Critical Success Factors
- Early engagement with chosen Notified Body
- Robust clinical evidence strategy and execution
- Comprehensive risk management throughout lifecycle
- Proactive post-market surveillance system
- Regular monitoring of regulatory updates and guidance
Common Pitfalls to Avoid
- Insufficient clinical evidence planning
- Late Notified Body engagement
- Inadequate post-market surveillance systems
- Poor documentation quality and traceability
- Underestimating timeline and resource requirements
FDA Submission Guide
FDA Medical Device Classification and Pathways
Class I Devices
- 510(k) Exempt - Most Class I devices
- General Controls apply (21 CFR 820)
- FDA registration required
- Device listing mandatory
Class II Devices
- 510(k) Clearance - Premarket notification
- General + Special Controls apply
- Predicate device identification required
- Substantial equivalence demonstration
Class III Devices
- PMA (Premarket Approval) - Full safety and effectiveness review
- IDE (Investigational Device Exemption) for clinical studies
- Clinical data typically required
- Post-market surveillance obligations
De Novo Classification
- Novel devices without predicate
- Low to moderate risk profile
- Creates new device classification
- Special controls development
Submission Pathways and Requirements
1. 510(k) Premarket Notification
Traditional 510(k)
- Predicate device comparison
- Performance testing documentation
- Software documentation (if applicable)
- Labeling and indications for use
Special 510(k)
- Modifications to cleared devices
- Design controls documentation
- Risk analysis of changes
- Performance validation
Abbreviated 510(k)
- Guidance document compliance
- Recognized standards conformance
- Special controls adherence
- Reduced documentation requirements
2. PMA (Premarket Approval)
Clinical Investigation Requirements
- IDE study protocol approval
- GCP compliance documentation
- Clinical study reports
- Statistical analysis plans
Manufacturing Information
- ISO 13485 QMS compliance
- Manufacturing process validation
- Facility inspection readiness
- Supply chain documentation
3. De Novo Classification Request
Risk-based Classification
- Benefit-risk profile analysis
- Predicate device absence justification
- Special controls recommendations
- Clinical evidence strategy
FDA Submission Process
Pre-Submission Activities
1. Q-Sub Meeting - Pre-submission consultation 2. Classification determination confirmation 3. Predicate device identification and analysis 4. Testing strategy development and validation 5. FDA guidance review and compliance assessment
Submission Preparation
1. Technical documentation compilation per FDA format 2. Quality system documentation and readiness 3. Clinical evidence compilation (if required) 4. Labeling and indications for use finalization 5. eCopy submission preparation
FDA Review Process
1. Administrative review (15 days for completeness) 2. Substantive review (90 days for 510(k), 180 days for PMA) 3. Additional information requests and responses 4. FDA questions and clarifications 5. Clearance/approval or denial decision
Special Considerations
Software as Medical Device (SaMD)
- Software documentation per FDA guidance
- Cybersecurity considerations and risk management
- Software lifecycle process documentation
- Change control procedures
Combination Products
- OPDP assignment determination
- Lead center coordination
- Intercenter agreement requirements
- Combination product specific guidance
HIPAA Compliance
- Protected Health Information safeguards
- Business associate agreements
- Risk assessment and management
- Breach notification procedures
Quality System Requirements
21 CFR Part 820 (QSR)
- Design controls (21 CFR 820.30)
- Document controls (21 CFR 820.40)
- Management responsibility (21 CFR 820.20)
- Corrective and preventive actions (21 CFR 820.100)
Key Performance Metrics
- Review timeline adherence and predictability
- First-time clearance rates and success factors
- Additional information request frequency
- Post-market compliance effectiveness
- FDA inspection readiness and outcomes
#!/usr/bin/env python3
"""
Regulatory Submission Tracking System
Automates monitoring and reporting of regulatory submission status
"""
import json
import datetime
from typing import Dict, List, Optional
from dataclasses import dataclass, asdict
from enum import Enum
class SubmissionType(Enum):
FDA_510K = "FDA_510K"
FDA_PMA = "FDA_PMA"
FDA_DE_NOVO = "FDA_DE_NOVO"
EU_MDR_CE = "EU_MDR_CE"
ISO_CERTIFICATION = "ISO_CERTIFICATION"
GLOBAL_REGULATORY = "GLOBAL_REGULATORY"
class SubmissionStatus(Enum):
PLANNING = "PLANNING"
IN_PREPARATION = "IN_PREPARATION"
SUBMITTED = "SUBMITTED"
UNDER_REVIEW = "UNDER_REVIEW"
ADDITIONAL_INFO_REQUESTED = "ADDITIONAL_INFO_REQUESTED"
APPROVED = "APPROVED"
REJECTED = "REJECTED"
WITHDRAWN = "WITHDRAWN"
@dataclass
class RegulatorySubmission:
submission_id: str
product_name: str
submission_type: SubmissionType
submission_status: SubmissionStatus
target_market: str
submission_date: Optional[datetime.date] = None
target_approval_date: Optional[datetime.date] = None
actual_approval_date: Optional[datetime.date] = None
regulatory_authority: str = ""
responsible_person: str = ""
notes: str = ""
last_updated: datetime.date = datetime.date.today()
class RegulatoryTracker:
def __init__(self, data_file: str = "regulatory_submissions.json"):
self.data_file = data_file
self.submissions: Dict[str, RegulatorySubmission] = {}
self.load_data()
def load_data(self):
"""Load existing submission data from JSON file"""
try:
with open(self.data_file, 'r') as f:
data = json.load(f)
for sub_id, sub_data in data.items():
# Convert date strings back to date objects
for date_field in ['submission_date', 'target_approval_date',
'actual_approval_date', 'last_updated']:
if sub_data.get(date_field):
sub_data[date_field] = datetime.datetime.strptime(
sub_data[date_field], '%Y-%m-%d').date()
# Convert enums
sub_data['submission_type'] = SubmissionType(sub_data['submission_type'])
sub_data['submission_status'] = SubmissionStatus(sub_data['submission_status'])
self.submissions[sub_id] = RegulatorySubmission(**sub_data)
except FileNotFoundError:
print(f"No existing data file found. Starting fresh.")
except Exception as e:
print(f"Error loading data: {e}")
def save_data(self):
"""Save submission data to JSON file"""
data = {}
for sub_id, submission in self.submissions.items():
sub_dict = asdict(submission)
# Convert date objects to strings
for date_field in ['submission_date', 'target_approval_date',
'actual_approval_date', 'last_updated']:
if sub_dict.get(date_field):
sub_dict[date_field] = sub_dict[date_field].strftime('%Y-%m-%d')
# Convert enums to strings
sub_dict['submission_type'] = sub_dict['submission_type'].value
sub_dict['submission_status'] = sub_dict['submission_status'].value
data[sub_id] = sub_dict
with open(self.data_file, 'w') as f:
json.dump(data, f, indent=2)
def add_submission(self, submission: RegulatorySubmission):
"""Add new regulatory submission"""
self.submissions[submission.submission_id] = submission
self.save_data()
print(f"Added submission: {submission.submission_id}")
def update_submission_status(self, submission_id: str,
new_status: SubmissionStatus,
notes: str = ""):
"""Update submission status"""
if submission_id in self.submissions:
self.submissions[submission_id].submission_status = new_status
self.submissions[submission_id].notes = notes
self.submissions[submission_id].last_updated = datetime.date.today()
self.save_data()
print(f"Updated {submission_id} status to {new_status.value}")
else:
print(f"Submission {submission_id} not found")
def get_submissions_by_status(self, status: SubmissionStatus) -> List[RegulatorySubmission]:
"""Get all submissions with specific status"""
return [sub for sub in self.submissions.values() if sub.submission_status == status]
def get_overdue_submissions(self) -> List[RegulatorySubmission]:
"""Get submissions that are overdue"""
today = datetime.date.today()
overdue = []
for submission in self.submissions.values():
if (submission.target_approval_date and
submission.target_approval_date < today and
submission.submission_status not in [SubmissionStatus.APPROVED,
SubmissionStatus.REJECTED,
SubmissionStatus.WITHDRAWN]):
overdue.append(submission)
return overdue
def generate_status_report(self) -> str:
"""Generate comprehensive status report"""
report = []
report.append("REGULATORY SUBMISSION STATUS REPORT")
report.append("=" * 50)
report.append(f"Generated: {datetime.date.today()}")
report.append("")
# Summary by status
status_counts = {}
for status in SubmissionStatus:
count = len(self.get_submissions_by_status(status))
if count > 0:
status_counts[status] = count
report.append("SUBMISSION STATUS SUMMARY:")
for status, count in status_counts.items():
report.append(f" {status.value}: {count}")
report.append("")
# Overdue submissions
overdue = self.get_overdue_submissions()
if overdue:
report.append("OVERDUE SUBMISSIONS:")
for submission in overdue:
days_overdue = (datetime.date.today() - submission.target_approval_date).days
report.append(f" {submission.submission_id} - {days_overdue} days overdue")
report.append("")
# Active submissions requiring attention
active_statuses = [SubmissionStatus.SUBMITTED, SubmissionStatus.UNDER_REVIEW,
SubmissionStatus.ADDITIONAL_INFO_REQUESTED]
active_submissions = []
for status in active_statuses:
active_submissions.extend(self.get_submissions_by_status(status))
if active_submissions:
report.append("ACTIVE SUBMISSIONS REQUIRING ATTENTION:")
for submission in active_submissions:
report.append(f" {submission.submission_id} - {submission.product_name}")
report.append(f" Status: {submission.submission_status.value}")
report.append(f" Target Date: {submission.target_approval_date}")
report.append(f" Authority: {submission.regulatory_authority}")
report.append("")
return "\n".join(report)
def main():
"""Main function for command-line usage"""
tracker = RegulatoryTracker()
# Generate and print status report
print(tracker.generate_status_report())
# Example: Add a new submission
# new_submission = RegulatorySubmission(
# submission_id="SUB-2024-001",
# product_name="HealthTech Device X",
# submission_type=SubmissionType.FDA_510K,
# submission_status=SubmissionStatus.PLANNING,
# target_market="United States",
# target_approval_date=datetime.date(2024, 12, 31),
# regulatory_authority="FDA",
# responsible_person="John Doe"
# )
# tracker.add_submission(new_submission)
if __name__ == "__main__":
main()