[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASA2PH9HG8ARK2J3JSYYDT":3,"skill-same:01M7ASA2PH9HG8ARK2J3JSYYDT":78},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M7ASA2PH9HG8ARK2J3JSYYDT","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 when working on document control procedures, change control workflows, document numbering, version management, electronic signature compliance, or regulatory documentation review.","GongYuanCaiJi\u002Fdsh-claude-skills","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7APPQ7AEZTDQB0N6HCPTR2X",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fquality-documentation-manager\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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 when working on document control procedures, change control workflows, 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 document & record control — ISO 13485 §4.2 under the QMSR (legacy QSR sections, historical)\n\n> **⚠️ STATUS — QMSR transition (effective 2026-02-02):** FDA's Quality Management System Regulation (QMSR) final rule (89 FR 7496) amended 21 CFR Part 820 to **incorporate ISO 13485:2016 by reference** and removed the legacy QSR subsection structure. The section numbers in the table below (820.40\u002F.180\u002F.181\u002F.184\u002F.186) **no longer exist in the CFR**; they are retained only as a familiar index. Current document\u002Frecord control authority is **ISO 13485:2016 §4.2** (esp. §4.2.4 control of documents, §4.2.5 control of records), with the medical device file in §4.2.3 and records additions in retained **21 CFR 820.35**. Cite the ISO 13485 clauses — not the 820.x numbers — in current compliance documentation.\n\n| Legacy QSR Section (historical, pre-2026) | Requirement | Current authority under QMSR (legacy QSR shown for index) |\n|-------------------------------------------|-------------|------------------------------|\n| 820.40 | Document controls | ISO 13485 §4.2.4 |\n| 820.180 | General record requirements | ISO 13485 §4.2.5 + 21 CFR 820.35 (retained) |\n| 820.181 | Device master record | ISO 13485 §4.2.3 (medical device file) |\n| 820.184 | Device history record | ISO 13485 §4.2.5 + 21 CFR 820.35 (retained) |\n| 820.186 | Quality system record | ISO 13485 §4.2.5 + 21 CFR 820.35 (retained) |\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\n> **Decision discipline:** The validator scripts in this skill check structure and completeness — they do not certify a document or record as compliant. Approval and release decisions are yours and the document owner's to make under your controlled procedure; route regulatory-classification or submission-record questions to Regulatory Affairs.\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 document & record control — ISO 13485 §4.2 under the QMSR (legacy QSR sections, historical)\n\n> **⚠️ STATUS — QMSR transition (effective 2026-02-02):** FDA's Quality Management System Regulation (QMSR) final rule (89 FR 7496) amended 21 CFR Part 820 to **incorporate ISO 13485:2016 by reference** and removed the legacy QSR subsection structure. The section numbers in the table below (820.40\u002F.180\u002F.181\u002F.184\u002F.186) **no longer exist in the CFR**; they are retained only as a familiar index. Current document\u002Frecord control authority is **ISO 13485:2016 §4.2** (esp. §4.2.4 control of documents, §4.2.5 control of records), with the medical device file in §4.2.3 and records additions in retained **21 CFR 820.35**. Cite the ISO 13485 clauses — not the 820.x numbers — in current compliance documentation.\n\n| Legacy QSR Section (historical, pre-2026) | Requirement | Current authority under QMSR (legacy QSR shown for index) |\n|-------------------------------------------|-------------|------------------------------|\n| 820.40 | Document controls | ISO 13485 §4.2.4 |\n| 820.180 | General record requirements | ISO 13485 §4.2.5 + 21 CFR 820.35 (retained) |\n| 820.181 | Device master record | ISO 13485 §4.2.3 (medical device file) |\n| 820.184 | Device history record | ISO 13485 §4.2.5 + 21 CFR 820.35 (retained) |\n| 820.186 | Quality system record | ISO 13485 §4.2.5 + 21 CFR 820.35 (retained) |\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\n> **Decision discipline:** The validator scripts in this skill check structure and completeness — they do not certify a document or record as compliant. Approval and release decisions are yours and the document owner's to make under your controlled procedure; route regulatory-classification or submission-record questions to Regulatory Affairs.\n",{"name":5,"triggers":24,"description":7},[25,26,27,28,29,30,31,32,33,34,35,36],"document control","document numbering","version control","change control","document approval","electronic signature","21 CFR Part 11","audit trail","document lifecycle","controlled document","document master list","record retention","main","992d25a425dee442a1f6a628d00a4fed33efe839","ra-qm-team\u002Fskills\u002Fquality-documentation-manager","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 04:26:20",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill quality-documentation-manager",{"tool":50,"command":51},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill quality-documentation-manager",{"tool":53,"command":54},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill quality-documentation-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fquality-documentation-manager\u002FSKILL.md",true,[58,64,68,74],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002F21cfr11-compliance-guide.md","REFERENCE","参考文档",13450,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fquality-documentation-manager\u002Freferences\u002F21cfr11-compliance-guide.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fdocument-control-procedures.md",12905,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fquality-documentation-manager\u002Freferences\u002Fdocument-control-procedures.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fdocument_validator.py","SCRIPT","脚本",22838,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fquality-documentation-manager\u002Fscripts\u002Fdocument_validator.py",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Fdocument_version_control.py",17024,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fquality-documentation-manager\u002Fscripts\u002Fdocument_version_control.py",[79,86,93,100,107,114],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7ASG5XZVP67CMMRENYFQWPW","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7ASFSGJF6G9KM40S1QJPR57","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7ASFFNCMS1X5X276VE277KW","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7ASF2BM8D9CDRQV1VBV7FV6","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7ASERRV1ES4S7QJRTTYWK0H","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7ASEANH3H547WQBZ7X8W5CX","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]