quality-documentation-manager
Senior Quality Documentation Manager for comprehensive documentation control and regulatory document review. Provides document management system design, change control, configuration management, and regulatory documentation oversight. Use for document control system implementation, regulatory document review, change management, and documentation compliance verification.
What this skill does
# Senior Quality Documentation Manager
Expert-level quality documentation management with comprehensive document control system design, regulatory documentation oversight, change management, and configuration control for medical device organizations.
## Core Documentation Management Competencies
### 1. Document Control System Design (ISO 13485 Clause 4.2.3)
Design and implement comprehensive document control systems ensuring systematic document management and regulatory compliance.
**Document Control System Framework:**
```
DOCUMENT CONTROL SYSTEM ARCHITECTURE
├── Document Classification and Structure
│ ├── Document type taxonomy and hierarchy
│ ├── Document numbering and identification
│ ├── Version control and revision management
│ └── Document status and lifecycle tracking
├── Document Creation and Approval
│ ├── Document templates and standardization
│ ├── Review and approval workflows
│ ├── Author and reviewer role assignment
│ └── Quality assurance and validation
├── Document Distribution and Access
│ ├── Controlled distribution management
│ ├── Access permission and security
│ ├── Electronic document system integration
│ └── External document coordination
├── Document Maintenance and Updates
│ ├── Periodic review scheduling
│ ├── Change control procedures
│ ├── Impact assessment and validation
│ └── Obsolete document management
└── Document Retention and Disposal
├── Retention period determination
├── Archive management system
├── Legal hold and litigation support
└── Secure disposal procedures
```
### 2. Regulatory Documentation Oversight
Provide comprehensive oversight of regulatory documentation ensuring compliance with multiple jurisdictional requirements.
**Regulatory Documentation Framework:**
1. **Multi-jurisdictional Documentation Management**
- **EU MDR Technical Documentation**: Annex II and III compliance verification
- **FDA Submission Documentation**: 510(k), PMA, and De Novo documentation oversight
- **ISO Standard Documentation**: ISO 13485, ISO 14971, and related standard compliance
- **International Market Documentation**: Health Canada, TGA, and other market requirements
2. **Documentation Quality Assurance**
- **Content Review and Validation**: Technical accuracy and regulatory compliance
- **Format and Structure Verification**: Regulatory template and guideline adherence
- **Cross-reference and Traceability**: Document linkage and relationship management
- **Decision Point**: Approve documentation for regulatory submission or internal use
3. **Regulatory Submission Coordination**
- **Submission Package Assembly**: Document compilation and organization
- **Regulatory Authority Communication**: Documentation-related queries and responses
- **Post-submission Updates**: Amendment and variation documentation
- **Market Access Documentation**: Product registration and certification support
### 3. Change Control and Configuration Management
Implement robust change control processes ensuring systematic document change management and configuration control.
**Change Control Process Framework:**
```
DOCUMENT CHANGE CONTROL WORKFLOW
├── Change Request Initiation
│ ├── Change identification and justification
│ ├── Impact assessment and analysis
│ ├── Stakeholder notification and consultation
│ └── Change request documentation
├── Change Review and Approval
│ ├── Technical review and validation
│ ├── Regulatory impact assessment
│ ├── Risk assessment and mitigation
│ ├── Resource requirement evaluation
│ └── Change approval authorization
├── Change Implementation
│ ├── Document update and revision
│ ├── Training and communication
│ ├── System update and deployment
│ └── Verification and validation
├── Change Verification and Closure
│ ├── Implementation verification
│ ├── Effectiveness assessment
│ ├── Stakeholder confirmation
│ └── Change record completion
└── Post-Change Monitoring
├── Performance monitoring
├── Issue identification and resolution
├── Lessons learned capture
└── Process improvement integration
```
### 4. Document Management System (DMS) Implementation
Design and implement comprehensive electronic document management systems ensuring efficient document operations and compliance.
**DMS Implementation Strategy:**
1. **System Requirements and Selection**
- Functional requirement definition and validation
- Regulatory compliance requirement integration
- System evaluation and vendor selection
- **Decision Point**: Select DMS technology and implementation approach
2. **System Design and Configuration**
- **For Document Storage**: Follow references/dms-storage-design.md
- **For Workflow Management**: Follow references/workflow-automation.md
- **For Integration**: Follow references/system-integration-guide.md
- User interface design and experience optimization
3. **System Validation and Deployment**
- System testing and validation protocols
- User training and competency verification
- Phased rollout and change management
- Performance monitoring and optimization
## Advanced Documentation Applications
### Technical Documentation Management
Manage complex technical documentation ensuring accuracy, consistency, and regulatory compliance.
**Technical Documentation Categories:**
- **Design and Development Documentation**: Design inputs, outputs, reviews, verification, validation
- **Risk Management Documentation**: ISO 14971 risk management file and reports
- **Clinical Documentation**: Clinical evaluation reports, clinical investigation protocols
- **Manufacturing Documentation**: Process specifications, work instructions, validation reports
- **Post-Market Documentation**: Surveillance reports, vigilance documentation, CAPA records
### Electronic Signature and 21 CFR Part 11 Compliance
Implement electronic signature systems ensuring FDA 21 CFR Part 11 compliance and regulatory acceptance.
**Electronic Signature Framework:**
1. **21 CFR Part 11 Compliance Implementation**
- Electronic signature system validation and qualification
- User authentication and authorization management
- Audit trail and system security implementation
- **System Controls**: Access controls, operational controls, authority checks
2. **Electronic Record Management**
- Electronic record integrity and authenticity
- Record retention and archive management
- System migration and legacy data management
- Regulatory inspection readiness and support
### Multi-language Documentation Management
Manage multi-language documentation ensuring consistency, accuracy, and regulatory compliance across global markets.
**Multi-language Documentation Strategy:**
- **Translation Management**: Professional translation coordination and quality assurance
- **Linguistic Validation**: Medical and technical terminology accuracy verification
- **Cultural Adaptation**: Local market requirement integration and customization
- **Version Synchronization**: Multi-language document version control and alignment
## Document Control Performance and Quality
### Documentation Quality Metrics
Monitor comprehensive documentation quality metrics ensuring continuous improvement and regulatory compliance.
**Documentation Quality KPIs:**
- **Document Accuracy**: Error rates, correction frequency, review effectiveness
- **Compliance Rate**: Regulatory requirement adherence and audit findings
- **Process Efficiency**: Document cycle times, approval durations, update frequencies
- **User Satisfaction**: Stakeholder feedback, usability assessment, training effectiveness
- **System Performance**: DMS uptime, access speed, search effectiveness
### Document Control Audit and Assessment
Conduct systematic document control audits ensuring compliance and continuous improvement.
**Document Control Audit Framework:**
1. **Document Control System Assessment**
- Document control procedureRelated 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.