[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KC1VRR5JTDBNZANHPS6VR6":3,"skill-same:01M6KC1VRR5JTDBNZANHPS6VR6":111},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":69,"commitSha":70,"skillDirectory":71,"forksCount":72,"repositoryHtmlUrl":73,"repositoryHomepageUrl":6,"ownerHtmlUrl":74,"ownerBlogUrl":75,"ownerDescription":6,"updatedAt":76,"install":77,"resources":90},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager",null,"Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"manager","documentation","quality documentation manager","quality","master","for","retention","change control","21 cfr part 11","cfr","medical","documentation review","system management","review","list","change management","system","audit","change","workflow","2026-11-10 10:12:30",false,"---\nname: \"quality-documentation-manager\"\ndescription: Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.\ntriggers:\n  - document control\n  - document numbering\n  - version control\n  - change control\n  - document approval\n  - electronic signature\n  - 21 CFR Part 11\n  - audit trail\n  - document lifecycle\n  - controlled document\n  - document master list\n  - record retention\n---\n\n# Quality Documentation Manager\n\nDocument control system design and management for ISO 13485-compliant quality management systems, including numbering conventions, approval workflows, change control, and electronic record compliance.\n\n---\n\n## Table of Contents\n\n- [Document Control Workflow](#document-control-workflow)\n- [Document Numbering System](#document-numbering-system)\n- [Approval and Review Process](#approval-and-review-process)\n- [Change Control Process](#change-control-process)\n- [21 CFR Part 11 Compliance](#21-cfr-part-11-compliance)\n- [Reference Documentation](#reference-documentation)\n- [Tools](#tools)\n\n---\n\n## Document Control Workflow\n\nImplement document control from creation through obsolescence:\n\n1. Assign document number per numbering procedure\n2. Create document using controlled template\n3. Route for review to required reviewers\n4. Address review comments and document responses\n5. Obtain required approval signatures\n6. Assign effective date and distribute\n7. Update Document Master List\n8. **Validation:** Document accessible at point of use; obsolete versions removed\n\n### Document Lifecycle Stages\n\n| Stage | Definition | Actions Required |\n|-------|------------|------------------|\n| Draft | Under creation or revision | Author editing, not for use |\n| Review | Circulated for review | Reviewers provide feedback |\n| Approved | All signatures obtained | Ready for training\u002Fdistribution |\n| Effective | Training complete, released | Available for use |\n| Superseded | Replaced by newer revision | Remove from active use |\n| Obsolete | No longer applicable | Archive per retention schedule |\n\n### Document Types and Prefixes\n\n| Prefix | Document Type | Typical Content |\n|--------|---------------|-----------------|\n| QM | Quality Manual | QMS overview, scope, policy |\n| SOP | Standard Operating Procedure | Process-level procedures |\n| WI | Work Instruction | Task-level step-by-step |\n| TF | Template\u002FForm | Controlled forms |\n| SPEC | Specification | Product\u002Fprocess specs |\n| PLN | Plan | Quality\u002Fproject plans |\n\n### Required Reviewers by Document Type\n\n| Document Type | Required Reviewers | Required Approvers |\n|---------------|-------------------|-------------------|\n| SOP | Process Owner, QA | QA Manager, Process Owner |\n| WI | Area Supervisor, QA | Area Manager |\n| SPEC | Engineering, QA | Engineering Manager, QA |\n| TF | Process Owner | QA |\n| Design Documents | Design Team, QA | Design Control Authority |\n\n---\n\n## Document Numbering System\n\nAssign consistent document numbers for identification and retrieval.\n\n### Numbering Format\n\nStandard format: `PREFIX-CATEGORY-SEQUENCE[-REVISION]`\n\n```\nExample: SOP-02-001-A\n\nSOP = Document type (Standard Operating Procedure)\n02  = Category code (Document Control)\n001 = Sequential number\nA   = Revision indicator\n```\n\n### Category Codes\n\n| Code | Functional Area | Description |\n|------|-----------------|-------------|\n| 01 | Quality Management | QMS procedures, management review |\n| 02 | Document Control | This area |\n| 03 | Human Resources | Training, competency |\n| 04 | Design & Development | Design control processes |\n| 05 | Purchasing | Supplier management |\n| 06 | Production | Manufacturing procedures |\n| 07 | Quality Control | Inspection, testing |\n| 08 | CAPA | Corrective\u002Fpreventive actions |\n| 09 | Risk Management | ISO 14971 processes |\n| 10 | Regulatory Affairs | Submissions, compliance |\n\n### Numbering Workflow\n\n1. Author requests document number from Document Control\n2. Document Control verifies category assignment\n3. Document Control assigns next available sequence number\n4. Number recorded in Document Master List\n5. Author creates document using assigned number\n6. **Validation:** Number format matches standard; no duplicates in Master List\n\n### Revision Designation\n\n| Change Type | Revision Increment | Example |\n|-------------|-------------------|---------|\n| Major revision | Increment number | Rev 01 → Rev 02 |\n| Minor revision | Increment sub-revision | Rev 01 → Rev 01.1 |\n| Administrative | No change or letter suffix | Rev 01 → Rev 01a |\n\nSee `references\u002Fdocument-control-procedures.md` for complete numbering guidance.\n\n---\n\n## Approval and Review Process\n\nObtain required reviews and approvals before document release.\n\n### Review Workflow\n\n1. Author completes document draft\n2. Author submits for review via routing form or DMS\n3. Reviewers assigned based on document type\n4. Reviewers provide comments within review period (5-10 business days)\n5. Author addresses comments and documents responses\n6. Author resubmits revised document\n7. Approvers sign and date\n8. **Validation:** All required reviewers completed; all comments addressed with documented disposition\n\n### Comment Disposition\n\n| Disposition | Action Required |\n|-------------|-----------------|\n| Accept | Incorporate comment as written |\n| Accept with modification | Incorporate with changes, document rationale |\n| Reject | Do not incorporate, document justification |\n| Defer | Address in future revision, document reason |\n\n### Approval Matrix\n\n```\nDocument Level 1 (Policy\u002FQM): CEO or delegate + QA Manager\nDocument Level 2 (SOP): Department Manager + QA Manager\nDocument Level 3 (WI\u002FTF): Area Supervisor + QA Representative\n```\n\n### Signature Requirements\n\n| Element | Requirement |\n|---------|-------------|\n| Name | Printed name of signer |\n| Signature | Handwritten or electronic signature |\n| Date | Date signature applied |\n| Role | Function\u002Frole of signer |\n\n---\n\n## Change Control Process\n\nManage document changes systematically through review and approval.\n\n### Change Control Workflow\n\n1. Identify need for document change\n2. Complete Change Request Form with justification\n3. Document Control assigns change number and logs request\n4. Route to reviewers for impact assessment\n5. Obtain approvals based on change classification\n6. Author implements approved changes\n7. Update revision number and change history\n8. **Validation:** Changes match approved scope; change history complete\n\n### Change Classification\n\n| Class | Definition | Approval Level | Examples |\n|-------|------------|----------------|----------|\n| Administrative | No content impact | Document Control | Typos, formatting |\n| Minor | Limited content change | Process Owner + QA | Clarifications |\n| Major | Significant content change | Full review cycle | New requirements |\n| Emergency | Urgent safety\u002Fcompliance | Expedited + retrospective | Safety issues |\n\n### Impact Assessment Checklist\n\n| Impact Area | Assessment Questions |\n|-------------|---------------------|\n| Training | Does change require retraining? |\n| Equipment | Does change affect equipment or systems? |\n| Validation | Does change require revalidation? |\n| Regulatory | Does change affect regulatory filings? |\n| Other Documents | Which related documents need updating? |\n| Records | What records are affected? |\n\n### Change History Documentation\n\nEach document must include change history:\n\n```\n| Revision | Date | Description | Author | Approver |\n|----------|------|-------------|--------|----------|\n| 01 | 2023-01-15 | Initial release | J. Smith | M. Jones |\n| 02 | 2024-03-01 | Updated workflow | J. Smith | M. Jones |\n```\n\n---\n\n## 21 CFR Part 11 Compliance\n\nImplement electronic record and signature controls for FDA compliance.\n\n### Part 11 Scope\n\n| Applies To | Does Not Apply To |\n|------------|-------------------|\n| Records required by FDA regulations | Paper records |\n| Records submitted to FDA | Internal non-regulated documents |\n| Electronic signatures on required records | General email communication |\n\n### Electronic Record Controls\n\n1. Validate system for accuracy and reliability\n2. Implement secure audit trail for all changes\n3. Restrict system access to authorized individuals\n4. Generate accurate copies in human-readable format\n5. Protect records throughout retention period\n6. **Validation:** Audit trail captures who, what, when for all changes\n\n### Audit Trail Requirements\n\n| Requirement | Implementation |\n|-------------|----------------|\n| Secure | Cannot be modified by users |\n| Computer-generated | System creates automatically |\n| Time-stamped | Date and time of each action |\n| Original values | Previous values retained |\n| User identity | Who made each change |\n\n### Electronic Signature Requirements\n\n| Requirement | Implementation |\n|-------------|----------------|\n| Unique to individual | Not shared between persons |\n| At least 2 components | User ID + password minimum |\n| Signature manifestation | Name, date\u002Ftime, meaning displayed |\n| Linked to record | Cannot be excised or copied |\n\n### Signature Manifestation\n\nEvery electronic signature must display:\n\n| Element | Example |\n|---------|---------|\n| Printed name | John Smith |\n| Date and time | 2024-03-15 14:32:05 EST |\n| Meaning | Approved for Release |\n\n### System Controls Checklist\n\n**Access Controls:**\n- [ ] Unique user ID for each person\n- [ ] Password complexity enforced\n- [ ] Account lockout after failed attempts\n- [ ] Session timeout after inactivity\n\n**Audit Trail:**\n- [ ] All record creation logged\n- [ ] All modifications logged with old\u002Fnew values\n- [ ] User identity captured\n- [ ] Date\u002Ftime stamp on all entries\n\n**Security:**\n- [ ] Role-based access control\n- [ ] Encryption for data at rest and in transit\n- [ ] Regular backup and tested recovery\n\nSee `references\u002F21cfr11-compliance-guide.md` for detailed compliance requirements.\n\n---\n\n## Reference Documentation\n\n### Document Control Procedures\n\n`references\u002Fdocument-control-procedures.md` contains:\n\n- Document numbering system and format\n- Document lifecycle stages and transitions\n- Review and approval workflow details\n- Change control process with classification criteria\n- Distribution and access control methods\n- Record retention periods and disposal procedures\n- Document Master List requirements\n\n### 21 CFR Part 11 Compliance Guide\n\n`references\u002F21cfr11-compliance-guide.md` contains:\n\n- Part 11 scope and applicability\n- Electronic record requirements (§11.10)\n- Electronic signature requirements (§11.50, 11.100, 11.200)\n- System control specifications\n- Validation approach and documentation\n- Compliance checklist and gap assessment template\n- Common FDA deficiencies and prevention\n\n---\n\n## Tools\n\n### Document Validator\n\n```bash\n# Validate document metadata\npython scripts\u002Fdocument_validator.py --doc document.json\n\n# Interactive validation mode\npython scripts\u002Fdocument_validator.py --interactive\n\n# JSON output for integration\npython scripts\u002Fdocument_validator.py --doc document.json --output json\n\n# Generate sample document JSON\npython scripts\u002Fdocument_validator.py --sample > sample_doc.json\n```\n\nValidates:\n- Document numbering convention compliance\n- Title and status requirements\n- Date validation (effective, review due)\n- Approval requirements by document type\n- Change history completeness\n- 21 CFR Part 11 controls (audit trail, signatures)\n\n### Sample Document Input\n\n```json\n{\n  \"number\": \"SOP-02-001\",\n  \"title\": \"Document Control Procedure\",\n  \"doc_type\": \"SOP\",\n  \"revision\": \"03\",\n  \"status\": \"Effective\",\n  \"effective_date\": \"2024-01-15\",\n  \"review_date\": \"2025-01-15\",\n  \"author\": \"J. Smith\",\n  \"approver\": \"M. Jones\",\n  \"change_history\": [\n    {\"revision\": \"01\", \"date\": \"2022-01-01\", \"description\": \"Initial release\"},\n    {\"revision\": \"02\", \"date\": \"2023-01-15\", \"description\": \"Updated workflow\"},\n    {\"revision\": \"03\", \"date\": \"2024-01-15\", \"description\": \"Added e-signature requirements\"}\n  ],\n  \"has_audit_trail\": true,\n  \"has_electronic_signature\": true,\n  \"signature_components\": 2\n}\n```\n\n---\n\n## Document Control Metrics\n\nTrack document control system performance.\n\n### Key Performance Indicators\n\n| Metric | Target | Calculation |\n|--------|--------|-------------|\n| Document cycle time | \u003C30 days | Average days from draft to effective |\n| Review completion rate | >95% | Reviews completed on time \u002F Total reviews |\n| Change request backlog | \u003C10 | Open change requests at month end |\n| Overdue review rate | \u003C5% | Documents past review date \u002F Total effective |\n| Audit finding rate | \u003C2 per audit | Document control findings per internal audit |\n\n### Periodic Review Schedule\n\n| Document Type | Review Frequency |\n|---------------|------------------|\n| Policy | Every 3 years |\n| SOP | Every 2 years |\n| WI | Every 2 years |\n| Specifications | As needed or with product changes |\n| Forms\u002FTemplates | Every 3 years |\n\n---\n\n## Regulatory Requirements\n\n### ISO 13485:2016 Clause 4.2\n\n| Sub-clause | Requirement |\n|------------|-------------|\n| 4.2.1 | Quality management system documentation |\n| 4.2.2 | Quality manual |\n| 4.2.3 | Medical device file (technical documentation) |\n| 4.2.4 | Control of documents |\n| 4.2.5 | Control of records |\n\n### FDA 21 CFR 820\n\n| Section | Requirement |\n|---------|-------------|\n| 820.40 | Document controls |\n| 820.180 | General record requirements |\n| 820.181 | Device master record |\n| 820.184 | Device history record |\n| 820.186 | Quality system record |\n\n### Common Audit Findings\n\n| Finding | Prevention |\n|---------|------------|\n| Obsolete documents in use | Implement distribution control |\n| Missing approval signatures | Enforce workflow before release |\n| Incomplete change history | Require history update with each revision |\n| No periodic review schedule | Establish and enforce review calendar |\n| Inadequate audit trail | Validate DMS for Part 11 compliance |\n","# Quality Documentation Manager\n\nDocument control system design and management for ISO 13485-compliant quality management systems, including numbering conventions, approval workflows, change control, and electronic record compliance.\n\n---\n\n## Table of Contents\n\n- [Document Control Workflow](#document-control-workflow)\n- [Document Numbering System](#document-numbering-system)\n- [Approval and Review Process](#approval-and-review-process)\n- [Change Control Process](#change-control-process)\n- [21 CFR Part 11 Compliance](#21-cfr-part-11-compliance)\n- [Reference Documentation](#reference-documentation)\n- [Tools](#tools)\n\n---\n\n## Document Control Workflow\n\nImplement document control from creation through obsolescence:\n\n1. Assign document number per numbering procedure\n2. Create document using controlled template\n3. Route for review to required reviewers\n4. Address review comments and document responses\n5. Obtain required approval signatures\n6. Assign effective date and distribute\n7. Update Document Master List\n8. **Validation:** Document accessible at point of use; obsolete versions removed\n\n### Document Lifecycle Stages\n\n| Stage | Definition | Actions Required |\n|-------|------------|------------------|\n| Draft | Under creation or revision | Author editing, not for use |\n| Review | Circulated for review | Reviewers provide feedback |\n| Approved | All signatures obtained | Ready for training\u002Fdistribution |\n| Effective | Training complete, released | Available for use |\n| Superseded | Replaced by newer revision | Remove from active use |\n| Obsolete | No longer applicable | Archive per retention schedule |\n\n### Document Types and Prefixes\n\n| Prefix | Document Type | Typical Content |\n|--------|---------------|-----------------|\n| QM | Quality Manual | QMS overview, scope, policy |\n| SOP | Standard Operating Procedure | Process-level procedures |\n| WI | Work Instruction | Task-level step-by-step |\n| TF | Template\u002FForm | Controlled forms |\n| SPEC | Specification | Product\u002Fprocess specs |\n| PLN | Plan | Quality\u002Fproject plans |\n\n### Required Reviewers by Document Type\n\n| Document Type | Required Reviewers | Required Approvers |\n|---------------|-------------------|-------------------|\n| SOP | Process Owner, QA | QA Manager, Process Owner |\n| WI | Area Supervisor, QA | Area Manager |\n| SPEC | Engineering, QA | Engineering Manager, QA |\n| TF | Process Owner | QA |\n| Design Documents | Design Team, QA | Design Control Authority |\n\n---\n\n## Document Numbering System\n\nAssign consistent document numbers for identification and retrieval.\n\n### Numbering Format\n\nStandard format: `PREFIX-CATEGORY-SEQUENCE[-REVISION]`\n\n```\nExample: SOP-02-001-A\n\nSOP = Document type (Standard Operating Procedure)\n02  = Category code (Document Control)\n001 = Sequential number\nA   = Revision indicator\n```\n\n### Category Codes\n\n| Code | Functional Area | Description |\n|------|-----------------|-------------|\n| 01 | Quality Management | QMS procedures, management review |\n| 02 | Document Control | This area |\n| 03 | Human Resources | Training, competency |\n| 04 | Design & Development | Design control processes |\n| 05 | Purchasing | Supplier management |\n| 06 | Production | Manufacturing procedures |\n| 07 | Quality Control | Inspection, testing |\n| 08 | CAPA | Corrective\u002Fpreventive actions |\n| 09 | Risk Management | ISO 14971 processes |\n| 10 | Regulatory Affairs | Submissions, compliance |\n\n### Numbering Workflow\n\n1. Author requests document number from Document Control\n2. Document Control verifies category assignment\n3. Document Control assigns next available sequence number\n4. Number recorded in Document Master List\n5. Author creates document using assigned number\n6. **Validation:** Number format matches standard; no duplicates in Master List\n\n### Revision Designation\n\n| Change Type | Revision Increment | Example |\n|-------------|-------------------|---------|\n| Major revision | Increment number | Rev 01 → Rev 02 |\n| Minor revision | Increment sub-revision | Rev 01 → Rev 01.1 |\n| Administrative | No change or letter suffix | Rev 01 → Rev 01a |\n\nSee `references\u002Fdocument-control-procedures.md` for complete numbering guidance.\n\n---\n\n## Approval and Review Process\n\nObtain required reviews and approvals before document release.\n\n### Review Workflow\n\n1. Author completes document draft\n2. Author submits for review via routing form or DMS\n3. Reviewers assigned based on document type\n4. Reviewers provide comments within review period (5-10 business days)\n5. Author addresses comments and documents responses\n6. Author resubmits revised document\n7. Approvers sign and date\n8. **Validation:** All required reviewers completed; all comments addressed with documented disposition\n\n### Comment Disposition\n\n| Disposition | Action Required |\n|-------------|-----------------|\n| Accept | Incorporate comment as written |\n| Accept with modification | Incorporate with changes, document rationale |\n| Reject | Do not incorporate, document justification |\n| Defer | Address in future revision, document reason |\n\n### Approval Matrix\n\n```\nDocument Level 1 (Policy\u002FQM): CEO or delegate + QA Manager\nDocument Level 2 (SOP): Department Manager + QA Manager\nDocument Level 3 (WI\u002FTF): Area Supervisor + QA Representative\n```\n\n### Signature Requirements\n\n| Element | Requirement |\n|---------|-------------|\n| Name | Printed name of signer |\n| Signature | Handwritten or electronic signature |\n| Date | Date signature applied |\n| Role | Function\u002Frole of signer |\n\n---\n\n## Change Control Process\n\nManage document changes systematically through review and approval.\n\n### Change Control Workflow\n\n1. Identify need for document change\n2. Complete Change Request Form with justification\n3. Document Control assigns change number and logs request\n4. Route to reviewers for impact assessment\n5. Obtain approvals based on change classification\n6. Author implements approved changes\n7. Update revision number and change history\n8. **Validation:** Changes match approved scope; change history complete\n\n### Change Classification\n\n| Class | Definition | Approval Level | Examples |\n|-------|------------|----------------|----------|\n| Administrative | No content impact | Document Control | Typos, formatting |\n| Minor | Limited content change | Process Owner + QA | Clarifications |\n| Major | Significant content change | Full review cycle | New requirements |\n| Emergency | Urgent safety\u002Fcompliance | Expedited + retrospective | Safety issues |\n\n### Impact Assessment Checklist\n\n| Impact Area | Assessment Questions |\n|-------------|---------------------|\n| Training | Does change require retraining? |\n| Equipment | Does change affect equipment or systems? |\n| Validation | Does change require revalidation? |\n| Regulatory | Does change affect regulatory filings? |\n| Other Documents | Which related documents need updating? |\n| Records | What records are affected? |\n\n### Change History Documentation\n\nEach document must include change history:\n\n```\n| Revision | Date | Description | Author | Approver |\n|----------|------|-------------|--------|----------|\n| 01 | 2023-01-15 | Initial release | J. Smith | M. Jones |\n| 02 | 2024-03-01 | Updated workflow | J. Smith | M. Jones |\n```\n\n---\n\n## 21 CFR Part 11 Compliance\n\nImplement electronic record and signature controls for FDA compliance.\n\n### Part 11 Scope\n\n| Applies To | Does Not Apply To |\n|------------|-------------------|\n| Records required by FDA regulations | Paper records |\n| Records submitted to FDA | Internal non-regulated documents |\n| Electronic signatures on required records | General email communication |\n\n### Electronic Record Controls\n\n1. Validate system for accuracy and reliability\n2. Implement secure audit trail for all changes\n3. Restrict system access to authorized individuals\n4. Generate accurate copies in human-readable format\n5. Protect records throughout retention period\n6. **Validation:** Audit trail captures who, what, when for all changes\n\n### Audit Trail Requirements\n\n| Requirement | Implementation |\n|-------------|----------------|\n| Secure | Cannot be modified by users |\n| Computer-generated | System creates automatically |\n| Time-stamped | Date and time of each action |\n| Original values | Previous values retained |\n| User identity | Who made each change |\n\n### Electronic Signature Requirements\n\n| Requirement | Implementation |\n|-------------|----------------|\n| Unique to individual | Not shared between persons |\n| At least 2 components | User ID + password minimum |\n| Signature manifestation | Name, date\u002Ftime, meaning displayed |\n| Linked to record | Cannot be excised or copied |\n\n### Signature Manifestation\n\nEvery electronic signature must display:\n\n| Element | Example |\n|---------|---------|\n| Printed name | John Smith |\n| Date and time | 2024-03-15 14:32:05 EST |\n| Meaning | Approved for Release |\n\n### System Controls Checklist\n\n**Access Controls:**\n- [ ] Unique user ID for each person\n- [ ] Password complexity enforced\n- [ ] Account lockout after failed attempts\n- [ ] Session timeout after inactivity\n\n**Audit Trail:**\n- [ ] All record creation logged\n- [ ] All modifications logged with old\u002Fnew values\n- [ ] User identity captured\n- [ ] Date\u002Ftime stamp on all entries\n\n**Security:**\n- [ ] Role-based access control\n- [ ] Encryption for data at rest and in transit\n- [ ] Regular backup and tested recovery\n\nSee `references\u002F21cfr11-compliance-guide.md` for detailed compliance requirements.\n\n---\n\n## Reference Documentation\n\n### Document Control Procedures\n\n`references\u002Fdocument-control-procedures.md` contains:\n\n- Document numbering system and format\n- Document lifecycle stages and transitions\n- Review and approval workflow details\n- Change control process with classification criteria\n- Distribution and access control methods\n- Record retention periods and disposal procedures\n- Document Master List requirements\n\n### 21 CFR Part 11 Compliance Guide\n\n`references\u002F21cfr11-compliance-guide.md` contains:\n\n- Part 11 scope and applicability\n- Electronic record requirements (§11.10)\n- Electronic signature requirements (§11.50, 11.100, 11.200)\n- System control specifications\n- Validation approach and documentation\n- Compliance checklist and gap assessment template\n- Common FDA deficiencies and prevention\n\n---\n\n## Tools\n\n### Document Validator\n\n```bash\n# Validate document metadata\npython scripts\u002Fdocument_validator.py --doc document.json\n\n# Interactive validation mode\npython scripts\u002Fdocument_validator.py --interactive\n\n# JSON output for integration\npython scripts\u002Fdocument_validator.py --doc document.json --output json\n\n# Generate sample document JSON\npython scripts\u002Fdocument_validator.py --sample > sample_doc.json\n```\n\nValidates:\n- Document numbering convention compliance\n- Title and status requirements\n- Date validation (effective, review due)\n- Approval requirements by document type\n- Change history completeness\n- 21 CFR Part 11 controls (audit trail, signatures)\n\n### Sample Document Input\n\n```json\n{\n  \"number\": \"SOP-02-001\",\n  \"title\": \"Document Control Procedure\",\n  \"doc_type\": \"SOP\",\n  \"revision\": \"03\",\n  \"status\": \"Effective\",\n  \"effective_date\": \"2024-01-15\",\n  \"review_date\": \"2025-01-15\",\n  \"author\": \"J. Smith\",\n  \"approver\": \"M. Jones\",\n  \"change_history\": [\n    {\"revision\": \"01\", \"date\": \"2022-01-01\", \"description\": \"Initial release\"},\n    {\"revision\": \"02\", \"date\": \"2023-01-15\", \"description\": \"Updated workflow\"},\n    {\"revision\": \"03\", \"date\": \"2024-01-15\", \"description\": \"Added e-signature requirements\"}\n  ],\n  \"has_audit_trail\": true,\n  \"has_electronic_signature\": true,\n  \"signature_components\": 2\n}\n```\n\n---\n\n## Document Control Metrics\n\nTrack document control system performance.\n\n### Key Performance Indicators\n\n| Metric | Target | Calculation |\n|--------|--------|-------------|\n| Document cycle time | \u003C30 days | Average days from draft to effective |\n| Review completion rate | >95% | Reviews completed on time \u002F Total reviews |\n| Change request backlog | \u003C10 | Open change requests at month end |\n| Overdue review rate | \u003C5% | Documents past review date \u002F Total effective |\n| Audit finding rate | \u003C2 per audit | Document control findings per internal audit |\n\n### Periodic Review Schedule\n\n| Document Type | Review Frequency |\n|---------------|------------------|\n| Policy | Every 3 years |\n| SOP | Every 2 years |\n| WI | Every 2 years |\n| Specifications | As needed or with product changes |\n| Forms\u002FTemplates | Every 3 years |\n\n---\n\n## Regulatory Requirements\n\n### ISO 13485:2016 Clause 4.2\n\n| Sub-clause | Requirement |\n|------------|-------------|\n| 4.2.1 | Quality management system documentation |\n| 4.2.2 | Quality manual |\n| 4.2.3 | Medical device file (technical documentation) |\n| 4.2.4 | Control of documents |\n| 4.2.5 | Control of records |\n\n### FDA 21 CFR 820\n\n| Section | Requirement |\n|---------|-------------|\n| 820.40 | Document controls |\n| 820.180 | General record requirements |\n| 820.181 | Device master record |\n| 820.184 | Device history record |\n| 820.186 | Quality system record |\n\n### Common Audit Findings\n\n| Finding | Prevention |\n|---------|------------|\n| Obsolete documents in use | Implement distribution control |\n| Missing approval signatures | Enforce workflow before release |\n| Incomplete change history | Require history update with each revision |\n| No periodic review schedule | Establish and enforce review calendar |\n| Inadequate audit trail | Validate DMS for Part 11 compliance |\n",{"name":5,"triggers":57,"description":7},[58,59,60,39,61,62,63,64,65,66,67,68],"document control","document numbering","version control","document approval","electronic signature","21 CFR Part 11","audit trail","document lifecycle","controlled document","document master list","record retention","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","ra-qm-team\u002Fquality-documentation-manager",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill quality-documentation-manager",{"tool":83,"command":84},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill quality-documentation-manager",{"tool":86,"command":87},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill quality-documentation-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",true,[91,97,101,107],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002F21cfr11-compliance-guide.md","REFERENCE","参考文档",13369,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002Freferences\u002F21cfr11-compliance-guide.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fdocument-control-procedures.md",11984,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002Freferences\u002Fdocument-control-procedures.md",{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fdocument_validator.py","SCRIPT","脚本",22838,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002Fscripts\u002Fdocument_validator.py",{"path":108,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":109,"sourceHtmlUrl":110},"scripts\u002Fdocument_version_control.py",17024,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002Fscripts\u002Fdocument_version_control.py",[112,138,162,186,214,233],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":52},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[118],{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[120,121,122,123,49,124,125,126,127,128,129,130,131,132,133,134,135,136,137,37],"compliance","soc2","soc2 compliance","audit evidence","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":52},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[145,146,147,148,149,150,151,152,126,127,153,154,42,155,156,157,158,159,160,161],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":52},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[169,170,171,172,173,174,175,176,177,127,178,179,180,181,182,183,184,185,32,37],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":198,"publishedAt":52},"01M6KC34Z8M1559EY1CXYBJB1A","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. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[192,195],{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":196,"categoryName":197,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师",[199,35,32,200,201,202,203,204,48,127,205,206,207,208,209,210,211,212,37,213],"quality manager qms iso13485","design","workflows","validation","actions","certification","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":221,"publishedAt":52},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[220],{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[222,35,32,45,223,224,225,226,120,227,48,228,170,229,230,231,154,209,37,232],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":239,"publishedAt":52},"01M6KC1PS7JKS8XK5ERT4M1VEN","qms-audit-expert","ISO 13485 internal audit expertise for medical device QMS. Covers audit planning, execution, nonconformity classification, and CAPA verification. Use for internal audit planning, audit execution, finding classification, external audit preparation, or audit program management.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fqms-audit-expert\u002FSKILL.md",[],[49,240,241,242,243,244,245,246,147,127,247,154,42,209,248,212,249,37,213,250],"qms audit expert","expert","planning","verification","execution","classification","schedule","checklist","audit preparation","prep","expertise"]