mdr-tech-doc-generator

Generates EU MDR Annex II/III technical documentation, GSPR checklists, and CER frameworks.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/HalseyYang/Skills-HY --skill mdr-tech-doc-generator-halseyyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mdr-tech-doc-generator
Source: https://github.com/HalseyYang/Skills-HY/tree/main/mdr-tech-doc-generator
Command: npx skills add https://github.com/HalseyYang/Skills-HY --skill mdr-tech-doc-generator-halseyyang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Preparing CE marking technical documentation under EU MDR 2017/745 requires assembling Annex II/III structures, GSPR compliance checklists, ISO 14971 risk management files, and clinical evaluation reports, which is slow and error-prone when done manually. ## Core Features & Use Cases - Technical Documentation Generation: Produces the seven-module MDR Annex II structure, 5-column GSPR checklists aligned with TEAM-NB expectations, and ISO 14971 risk management templates. - 2026 Regulatory Coverage: Integrates EUDAMED mandatory registration (2026-05-28), EU AI Act 2024/1689 high-risk AI obligations, MDR Annex I §17.2 cybersecurity, and MDCG 2026-4 SSCP upload duties. - Gap Analysis Script: Runs mdr_gap_analyzer.py to assess compliance gaps by device class and output prioritized recommendations in text or JSON. - Use Case: A manufacturer preparing a Class IIb device submission asks for a complete technical documentation skeleton with GSPR checklist, CER structure, and EUDAMED registration data requirements. ## Quick Start Ask the assistant to generate an MDR Annex II technical documentation framework with a GSPR checklist and CER structure for your device, providing its name, classification, and intended purpose.

Frequently Asked Questions about mdr-tech-doc-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate MDR Annex II technical documentation?

Provide the device name, classification, intended purpose, and whether it contains software, AI, or network connectivity. The skill outputs the seven-module Annex II structure, a GSPR checklist, risk management template, and CER framework aligned with TEAM-NB expectations.

What is a GSPR checklist under EU MDR?

A GSPR checklist maps each General Safety and Performance Requirement in MDR Annex I to its compliance method and evidence location. This skill uses the TEAM-NB 5-column format including a version and date column, and requires justification for any not-applicable entries.

Does the skill cover EU AI Act requirements for medical AI devices?

Yes, it covers EU AI Act 2024/1689 high-risk AI obligations integrated with MDR, including data governance, human oversight, algorithm validation, and Annex IV technical documentation. Post-Omnibus deadlines are 2027-12-02 for standalone AI and 2028-08-02 for AI embedded in MDR devices.

How do I run the MDR gap analysis script?

Run mdr_gap_analyzer.py with --device and --class arguments, or use --interactive for a guided session. It outputs a gap report by category with critical gaps and recommendations, in text or JSON format.

When is EUDAMED registration mandatory for medical devices?

EUDAMED Actor, UDI/device, NB certificate, and market surveillance modules became mandatory on 2026-05-28 for new devices, with legacy devices required to register by 2026-11-28. Devices not registered cannot be legally placed on the EU market.

What are the limitations of this MDR documentation skill?

It generates documentation frameworks and templates, not legal advice, and does not replace the PRRC's statutory responsibilities. For AI Act exemption clauses and pending proposals like COM(2025) 1023, users must verify against the latest official texts.