iso13485-audit-prep

Overview of iso13485-audit-prep skill

What iso13485-audit-prep is for

iso13485-audit-prep is a compliance review skill for pressure-testing an ISO 13485 medical-device quality management system before an internal audit, regulatory alignment review, product launch, CAPA follow-up, or post-market event review. It is built around a short set of auditor-style forcing questions rather than a broad ISO 13485 explainer, which makes it useful when you need to find weak evidence fast.

Best-fit users and audit moments

This skill is best for quality, regulatory, clinical, engineering, and compliance teams preparing for Clause 8.2.4 internal audits, MDR / FDA QSR alignment checks, DHF closure reviews, CAPA effectiveness verification, recall follow-up, or regulatory submission readiness. It is especially relevant if your risk is not “we do not know ISO 13485,” but “we may have gaps in traceability, CAPA evidence, complaint linkage, supplier control, or post-market surveillance.”

What makes the skill different from a generic prompt

A generic audit prompt often produces a checklist. The iso13485-audit-prep skill is narrower and more adversarial: it asks for evidence around design history files, CAPAs, complaint handling, supplier qualification, management review, and post-market signals. That framing helps reveal missing objective evidence, unclear ownership, weak effectiveness checks, and traceability breaks before an auditor or notified body does.

Important adoption caveat

The repository provides the skill content primarily in SKILL.md; there are no bundled scripts, reference folders, or helper templates in the current file tree. Treat iso13485-audit-prep as an expert interrogation pattern you apply to your own QMS artifacts, not as a complete audit management system or a substitute for qualified regulatory judgment.

How to Use iso13485-audit-prep skill

iso13485-audit-prep install context

If your environment supports GitHub-hosted skills, install from the repository path for alirezarezvani/claude-skills and target compliance-os/skills/iso13485-audit-prep. In many skill managers, the install pattern is similar to npx skills add alirezarezvani/claude-skills --skill iso13485-audit-prep, but confirm the command used by your local skill runner. After install, read SKILL.md first because it contains the command name, trigger shape, run timing, and the six QMS question areas.

Inputs the skill needs for useful output

For strong iso13485-audit-prep usage, do not ask “prepare me for ISO 13485.” Provide scope, product class, audit trigger, sites or processes, sample size, and the evidence you can share. Useful inputs include DHF index, design input-output traceability matrix, verification and validation summaries, latest CAPA list, complaint trend report, supplier quality records, management review minutes, PMS / PMCF summaries, recall or field action files, and previous audit findings.

A stronger invocation looks like: “Use /cs:iso13485-audit-prep for a Class IIb device DHF closure audit before EU MDR submission. Focus on design validation, CAPA effectiveness, complaint-to-risk-file linkage, and supplier controls. I can provide redacted DHF tables, five CAPA summaries, complaint trends, and the latest management review outputs. Return likely audit findings, missing evidence, and priority remediation actions.”

Suggested workflow for a review session

Start with a narrow scope: one device family, one site, one submission, or one audit window. Ask the skill to run the six-question review, then handle each area as a mini-audit. For DHFs, request a sample-based evidence challenge: design plan, inputs, outputs, verification, validation, transfer, changes, and traceability to user needs and clinical evidence. For CAPA, ask it to distinguish containment, correction, corrective action, root cause, and effectiveness verification.

After the first pass, turn each suspected gap into an evidence request: “What exact record would close this finding?” or “What would an auditor expect to see for objective evidence?” This keeps the output actionable instead of becoming a high-level compliance narrative.

Repository reading path before use

Because the skill has a single main file, read SKILL.md closely before relying on it. Pay attention to the “When to Run” section and the named audit pressure points. There are no separate rules/, references/, resources/, or scripts/ directories to inspect in the current structure, so you should bring your organization’s SOPs, quality manual, risk management file, and regulatory interpretation into the prompt.

iso13485-audit-prep skill FAQ

Is iso13485-audit-prep for Compliance Review or full certification prep?

iso13485-audit-prep for Compliance Review is the better framing. It can help you identify likely audit weaknesses and missing evidence, but it does not replace a complete certification readiness program, internal audit schedule, competent auditor, or legal/regulatory review. Use it as a pre-audit challenge layer before formal review.

Can beginners use this skill?

Yes, but beginners should pair it with their organization’s SOP map and a basic ISO 13485 clause understanding. The skill assumes concepts like DHF, CAPA, effectiveness verification, complaint handling, post-market surveillance, and management review. If those terms are unfamiliar, ask the model to explain each finding in plain language and map it to the record type your QMS should contain.

When should I not use this skill?

Do not use it for non-medical-device quality systems, purely software security audits, or generic ISO 9001 reviews unless you intentionally adapt the output. Also avoid using it as the sole basis for regulatory claims, audit responses, CAPA closure, or notified body communication. It is best at surfacing questions and evidence gaps, not making final compliance determinations.

How is it better than asking for an ISO 13485 checklist?

A checklist tells you what should exist. This skill pushes on whether evidence is complete, traceable, recent, sampled appropriately, and defensible under audit pressure. That matters because many ISO 13485 findings are not caused by total absence of process, but by weak linkage between design controls, risk management, CAPA, complaints, suppliers, management review, and post-market action.

How to Improve iso13485-audit-prep skill

Improve iso13485-audit-prep outputs with sharper scope

The fastest way to improve iso13485-audit-prep results is to replace broad scope with audit-specific context. Include device type, regulatory market, product class, lifecycle stage, audit date, prior findings, and the records available. “Review our QMS” is too broad; “challenge readiness for a Class III implant DHF closure and CAPA effectiveness review before notified body audit” gives the skill enough constraints to prioritize.

Provide evidence summaries, not just intentions

The skill works best when it can compare claims to records. Instead of saying “CAPAs are closed,” provide a table with CAPA ID, source, root cause method, correction, corrective action, due date, effectiveness criteria, verification date, linked complaints, and residual risk decision. For DHF review, provide a traceability snapshot from user needs through design inputs, outputs, verification, validation, risk controls, and clinical evidence.

Watch for common failure modes

The most common weak outputs come from missing sample data, unclear jurisdiction, or prompts that ask for “everything.” Another failure mode is accepting generic remediation such as “improve documentation.” Push for auditor-grade specificity: missing record, affected clause or process, risk level, owner, due date, and evidence needed for closure. If the answer sounds like a policy essay, ask for a finding register instead.

Iterate after the first audit pass

After the first response, ask the skill to separate critical findings from documentation improvements, identify which gaps could block launch or certification, and draft follow-up questions for process owners. Then rerun the review with newly supplied evidence. The value of this iso13485-audit-prep guide is not a single answer; it is the repeatable pressure-test loop that turns rough QMS confidence into defensible audit readiness.