regulatory-affairs-head
by alirezarezvaniregulatory-affairs-head is a Claude skill for medical device and HealthTech regulatory planning, including FDA 510(k), De Novo, PMA, EU MDR technical documentation, CE marking, global pathways, ISO mapping, deficiency responses, and submission tracking with included references and scripts.
This skill scores 80/100, making it a solid listing candidate for directory users who need an agent to structure medical-device regulatory planning and submission work. It provides enough triggers, workflows, reference material, and tooling to offer more leverage than a generic prompt, though users should account for installation/documentation gaps and the need to verify regulatory outputs carefully.
- Strong triggerability: frontmatter names concrete use cases such as FDA submission, EU MDR, 510(k), PMA approval, CE marking, regulatory pathway, and notified body work.
- Substantial operational content: SKILL.md is large and structured with workflows for regulatory strategy, FDA submissions, EU MDR submissions, global market access, regulatory intelligence, and decision frameworks.
- Useful supporting materials: four reference guides cover FDA, EU MDR, global regulatory pathways, and ISO requirements, plus scripts for pathway analysis and submission tracking.
- No install command or README is present in the skill path, so adoption depends on users already knowing how to install skills from this repository.
- Repository signals include a placeholder marker (“tbd”) and limited explicit constraints, which is a concern for a high-stakes regulatory domain.
Overview of regulatory-affairs-head skill
What regulatory-affairs-head is for
regulatory-affairs-head is a Claude skill for medical device and HealthTech regulatory work: pathway selection, submission planning, FDA 510(k)/De Novo/PMA preparation, EU MDR technical documentation, CE marking strategy, notified body responses, and global market access planning. It is best suited for founders, regulatory affairs teams, quality leaders, product managers, and consultants who need structured regulatory reasoning rather than a generic “write a submission plan” prompt.
Best-fit regulatory work
Use the regulatory-affairs-head skill when you need to turn a device concept, design change, software feature, or market expansion plan into a regulatory strategy. Strong fits include FDA predicate analysis, EU MDR classification, clinical evidence gap review, pre-submission meeting preparation, deficiency response drafting, ISO standards mapping, and sequencing approvals across FDA, EU MDR, Health Canada, PMDA, NMPA, TGA, or other markets.
What makes this skill different
The repository includes more than a role prompt. It contains workflow guidance in SKILL.md, reference guides for FDA, EU MDR, global pathways, and ISO requirements, plus helper scripts for pathway analysis and submission tracking. That makes it more useful for repeatable regulatory planning than a one-off prompt, especially when you need consistent decision logic across products or markets.
Important adoption cautions
This skill can improve regulatory drafting and planning, but it is not a substitute for licensed regulatory counsel, notified body feedback, FDA interaction, or a current standards search. Regulatory requirements change, and device-specific facts drive outcomes. Treat outputs as working drafts, decision support, and checklist material that must be verified against current guidance, applicable regulations, and your quality management system.
How to Use regulatory-affairs-head skill
regulatory-affairs-head install and repository path
Install from the GitHub skill repository with:
npx skills add alirezarezvani/claude-skills --skill regulatory-affairs-head
The skill lives at ra-qm-team/skills/regulatory-affairs-head. After install, read SKILL.md first, then review the reference files most relevant to your target market: references/fda-submission-guide.md, references/eu-mdr-submission-guide.md, references/global-regulatory-pathways.md, and references/iso-regulatory-requirements.md. If you need tooling, inspect scripts/regulatory_pathway_analyzer.py and scripts/regulatory_tracker.py.
Inputs the skill needs for reliable output
For high-quality regulatory-affairs-head usage, provide concrete device facts instead of asking broad questions. Include device name, intended use, patient population, user type, risk class estimate, invasiveness, implantable status, sterile status, software or AI/ML components, predicate availability, target markets, claims, clinical evidence, standards already considered, and desired deliverable.
A weak prompt is: “Create an FDA strategy for my device.”
A stronger prompt is: “Use regulatory-affairs-head for Regulatory Affairs planning. Device: cloud-connected wearable ECG patch for adult arrhythmia monitoring. US launch first, EU next. Software component with algorithmic event detection, no closed-loop therapy, non-sterile skin contact, 7-day wear, predicate candidates include [names]. Draft a 510(k) versus De Novo pathway assessment, testing evidence table, pre-sub questions, and risks that could change the pathway.”
Practical workflow for first use
Start with pathway classification before drafting submission content. Ask the skill to identify assumptions, missing facts, and pathway options, then request a table comparing likely routes by evidence burden, review body, timeline risk, and documentation impact. For FDA work, move from classification to predicate comparison, performance testing, software documentation, labeling, and pre-sub questions. For EU MDR, move from classification to conformity assessment route, Annex II technical documentation, clinical evaluation, PMS/PMCF, UDI, and notified body readiness.
If you are evaluating multiple markets, ask for a staged market access plan rather than a single global answer. Regulatory sequencing often changes because evidence generated for one authority may or may not satisfy another.
Using the scripts and references
The regulatory_pathway_analyzer.py script is useful when you want a structured first-pass pathway recommendation from device attributes. Run it locally from the skill directory, using interactive mode or a JSON device profile if supported in your environment. Use its output as an input to Claude, not as the final answer. The regulatory_tracker.py script is more operational: it can help model submission statuses, responsible owners, target approval dates, and authority interactions.
For best results, ask Claude to cite which repository reference it is applying, then have it separate “repository-based guidance,” “assumptions,” and “needs verification.”
regulatory-affairs-head skill FAQ
Is regulatory-affairs-head only for FDA submissions?
No. FDA 510(k), De Novo, and PMA work is a major use case, but the skill also covers EU MDR, CE marking, ISO regulatory requirements, Health Canada, PMDA, NMPA, TGA, and broader global market access planning. It is strongest when you specify the target jurisdictions and ask for market-by-market differences.
How is this better than an ordinary regulatory prompt?
An ordinary prompt may produce a plausible narrative but often misses workflow order, evidence tables, standards mapping, or region-specific documentation differences. The regulatory-affairs-head skill gives Claude a defined regulatory affairs role, trigger terms, submission workflows, reference material, and related scripts, which reduces guesswork and improves consistency across repeated regulatory tasks.
Can beginners use this skill?
Yes, but beginners should ask for explanations of assumptions and terms. Good beginner prompts request a “regulatory pathway briefing,” “missing information checklist,” or “submission readiness gap analysis” before asking for final documents. Avoid jumping straight to a 510(k), PMA, or MDR technical file draft unless your device profile and evidence set are already clear.
When should I not use regulatory-affairs-head?
Do not use it as the sole basis for final regulatory decisions, legal positions, clinical study obligations, or agency submissions. It is also a poor fit for pharmaceuticals, biologics, food regulation, cosmetics, or general corporate compliance unless the task directly touches medical device regulatory affairs. If your project depends on a recent guidance change, verify the current authority source before relying on the output.
How to Improve regulatory-affairs-head skill
Improve regulatory-affairs-head outputs with better facts
The most common failure mode is under-specified device context. Improve outputs by adding the intended purpose statement, indications for use, mechanism of action, patient-contact details, software safety class, cybersecurity relevance, clinical claims, prior clearances, target geography, and launch timeline. The skill can reason better when it knows whether you need a board-level strategy, a submission checklist, a deficiency response, or a technical documentation section.
Ask for decision tables, not just narrative
For regulatory-affairs-head guide-style work, request tables that expose tradeoffs: pathway option, rationale, evidence needed, major risks, expected authority questions, owner, and next action. This is especially useful for 510(k) versus De Novo, MDR Class IIa versus IIb, clinical investigation need, predicate strength, or multi-market launch sequencing.
Iterate after the first answer
Do not accept the first response as final. Ask the skill to identify weak assumptions, missing documents, and questions a reviewer or notified body would ask. Then provide additional evidence and request a revised version. A strong second-pass prompt is: “Revise the strategy using this predicate comparison and bench testing summary. Flag any claims not supported by the evidence and rewrite the submission plan to reduce reviewer objections.”
Add organization-specific constraints
The repository provides general regulatory workflows. Your best results come from layering in your company’s constraints: QMS maturity, ISO 13485 status, clinical budget, target launch date, existing test reports, outsourcing model, notified body availability, and risk tolerance. This turns regulatory-affairs-head from a generic regulatory assistant into a practical planning tool for your actual market access program.