quality-manager-qms-iso13485
ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support.
What this skill does
# Quality Manager - QMS ISO 13485 Specialist ISO 13485:2016 Quality Management System implementation, maintenance, and certification support for medical device organizations. --- ## Table of Contents - [QMS Implementation Workflow](#qms-implementation-workflow) - [Document Control Workflow](#document-control-workflow) - [Internal Audit Workflow](#internal-audit-workflow) - [Process Validation Workflow](#process-validation-workflow) - [Supplier Qualification Workflow](#supplier-qualification-workflow) - [QMS Process Reference](#qms-process-reference) - [Decision Frameworks](#decision-frameworks) - [Tools and References](#tools-and-references) --- ## QMS Implementation Workflow Implement ISO 13485:2016 compliant quality management system from gap analysis through certification. ### Workflow: Initial QMS Implementation 1. Conduct gap analysis against ISO 13485:2016 requirements 2. Document current state vs. required state for each clause 3. Prioritize gaps by: - Regulatory criticality - Risk to product safety - Resource requirements 4. Develop implementation roadmap with milestones 5. Establish Quality Manual per Clause 4.2.2: - QMS scope with justified exclusions - Process interactions - Procedure references 6. Create required documented procedures: - Document control (4.2.3) - Record control (4.2.4) - Internal audit (8.2.4) - Nonconforming product (8.3) - Corrective action (8.5.2) - Preventive action (8.5.3) 7. Deploy processes with training 8. **Validation:** Gap analysis complete; Quality Manual approved; all required procedures documented and trained ### Gap Analysis Matrix | Clause | Requirement | Current State | Gap | Priority | Action | |--------|-------------|---------------|-----|----------|--------| | 4.2.2 | Quality Manual | Not documented | Major | High | Create QM | | 4.2.3 | Document control | Informal | Moderate | High | Formalize SOP | | 5.6 | Management review | Ad hoc | Major | High | Establish schedule | | 7.3 | Design control | Partial | Moderate | Medium | Complete procedures | | 8.2.4 | Internal audit | None | Major | High | Create program | ### QMS Structure | Level | Document Type | Purpose | Example | |-------|---------------|---------|---------| | 1 | Quality Manual | QMS overview, policy | QM-001 | | 2 | Procedures | How processes work | SOP-02-001 | | 3 | Work Instructions | Task-level detail | WI-06-012 | | 4 | Records | Evidence of conformity | Training records | ### Required Procedure List | Clause | Procedure | Minimum Content | |--------|-----------|-----------------| | 4.2.3 | Document Control | Approval, review, distribution, obsolete control | | 4.2.4 | Record Control | Identification, storage, retention, disposal | | 8.2.4 | Internal Audit | Program, auditor qualification, reporting | | 8.3 | Nonconforming Product | Identification, segregation, disposition | | 8.5.2 | Corrective Action | Investigation, root cause, effectiveness | | 8.5.3 | Preventive Action | Risk identification, implementation, verification | --- ## Document Control Workflow Establish and maintain document control per ISO 13485 Clause 4.2.3. ### Workflow: Document Creation and Approval 1. Identify need for new document or revision 2. Assign document number per numbering convention: - Format: `[TYPE]-[AREA]-[SEQUENCE]-[REV]` - Example: `SOP-02-001-01` 3. Draft document using approved template 4. Route for review to subject matter experts 5. Collect and address review comments 6. Obtain required approvals based on document type 7. Update Document Master List 8. **Validation:** Document numbered correctly; all reviewers signed; Master List updated ### Document Numbering Convention | Prefix | Document Type | Approval Authority | |--------|---------------|-------------------| | QM | Quality Manual | Management Rep + CEO | | POL | Policy | Department Head + QA | | SOP | Procedure | Process Owner + QA | | WI | Work Instruction | Supervisor + QA | | TF | Template/Form | Process Owner | | SPEC | Specification | Engineering + QA | ### Area Codes | Code | Area | Examples | |------|------|----------| | 01 | Quality Management | Quality Manual, policy | | 02 | Document Control | This procedure | | 03 | Training | Competency procedures | | 04 | Design | Design control | | 05 | Purchasing | Supplier management | | 06 | Production | Manufacturing | | 07 | Quality Control | Inspection, testing | | 08 | CAPA | Corrective actions | ### Document Change Control | Change Type | Approval Level | Examples | |-------------|----------------|----------| | Administrative | Document Control | Typos, formatting | | Minor | Process Owner + QA | Clarifications | | Major | Full review cycle | Process changes | | Emergency | Expedited + retrospective | Safety issues | ### Document Review Schedule | Document Type | Review Period | Trigger for Unscheduled Review | |---------------|---------------|-------------------------------| | Quality Manual | Annual | Organizational change | | Procedures | Annual | Audit finding, regulation change | | Work Instructions | 2 years | Process change | | Forms | 2 years | User feedback | --- ## Internal Audit Workflow Plan and execute internal audits per ISO 13485 Clause 8.2.4. ### Workflow: Annual Audit Program 1. Identify processes and areas requiring audit coverage 2. Assess risk factors for audit frequency: - Previous audit findings - Regulatory changes - Process changes - Complaint trends 3. Assign qualified auditors (independent of area audited) 4. Develop annual audit schedule 5. Obtain management approval 6. Communicate schedule to process owners 7. Track completion and reschedule as needed 8. **Validation:** All processes covered; auditors qualified and independent; schedule approved ### Workflow: Individual Audit Execution 1. Prepare audit plan with scope, criteria, and schedule 2. Notify auditee minimum 1 week prior 3. Review procedures and previous audit results 4. Prepare audit checklist 5. Conduct opening meeting 6. Collect evidence through: - Document review - Record sampling - Process observation - Personnel interviews 7. Classify findings: - Major NC: Absence or breakdown of system - Minor NC: Single lapse or deviation - Observation: Risk of future NC 8. Conduct closing meeting 9. Issue audit report within 5 business days 10. **Validation:** All checklist items addressed; findings supported by evidence; report distributed ### Audit Program Template | Audit # | Process | Clauses | Q1 | Q2 | Q3 | Q4 | Auditor | |---------|---------|---------|----|----|----|----|---------| | IA-001 | Document Control | 4.2.3, 4.2.4 | X | | | | [Name] | | IA-002 | Management Review | 5.6 | | X | | | [Name] | | IA-003 | Design Control | 7.3 | | X | | | [Name] | | IA-004 | Production | 7.5 | | | X | | [Name] | | IA-005 | CAPA | 8.5.2, 8.5.3 | | | | X | [Name] | ### Auditor Qualification Requirements | Criterion | Requirement | |-----------|-------------| | Training | ISO 13485 awareness + auditor training | | Experience | Minimum 1 audit as observer | | Independence | Not auditing own work area | | Competence | Understanding of audited process | ### Finding Classification Guide | Classification | Criteria | Response Time | |----------------|----------|---------------| | Major NC | System absence, total breakdown, regulatory violation | 30 days for CAPA | | Minor NC | Single instance, partial compliance | 60 days for CAPA | | Observation | Potential risk, improvement opportunity | Track in next audit | --- ## Process Validation Workflow Validate special processes per ISO 13485 Clause 7.5.6. ### Workflow: Process Validation Protocol 1. Identify processes requiring validation: - Output cannot be verified by inspection - Deficiencies appear only in use - Sterilization, welding, sealing, software 2. Form validation team with subject matter experts 3. Write validation protocol including: - Process description and parameters -
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.