Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
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.
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.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Document control system design and management for ISO 13485-compliant quality management systems, including numbering conventions, approval workflows, change control, and electronic record compliance.
Document Control Workflow Document Numbering System Approval and Review Process Change Control Process 21 CFR Part 11 Compliance Reference Documentation Tools
Implement document control from creation through obsolescence: Assign document number per numbering procedure Create document using controlled template Route for review to required reviewers Address review comments and document responses Obtain required approval signatures Assign effective date and distribute Update Document Master List Validation: Document accessible at point of use; obsolete versions removed
StageDefinitionActions RequiredDraftUnder creation or revisionAuthor editing, not for useReviewCirculated for reviewReviewers provide feedbackApprovedAll signatures obtainedReady for training/distributionEffectiveTraining complete, releasedAvailable for useSupersededReplaced by newer revisionRemove from active useObsoleteNo longer applicableArchive per retention schedule
PrefixDocument TypeTypical ContentQMQuality ManualQMS overview, scope, policySOPStandard Operating ProcedureProcess-level proceduresWIWork InstructionTask-level step-by-stepTFTemplate/FormControlled formsSPECSpecificationProduct/process specsPLNPlanQuality/project plans
Document TypeRequired ReviewersRequired ApproversSOPProcess Owner, QAQA Manager, Process OwnerWIArea Supervisor, QAArea ManagerSPECEngineering, QAEngineering Manager, QATFProcess OwnerQADesign DocumentsDesign Team, QADesign Control Authority
Assign consistent document numbers for identification and retrieval.
Standard format: PREFIX-CATEGORY-SEQUENCE[-REVISION] Example: SOP-02-001-A SOP = Document type (Standard Operating Procedure) 02 = Category code (Document Control) 001 = Sequential number A = Revision indicator
CodeFunctional AreaDescription01Quality ManagementQMS procedures, management review02Document ControlThis area03Human ResourcesTraining, competency04Design & DevelopmentDesign control processes05PurchasingSupplier management06ProductionManufacturing procedures07Quality ControlInspection, testing08CAPACorrective/preventive actions09Risk ManagementISO 14971 processes10Regulatory AffairsSubmissions, compliance
Author requests document number from Document Control Document Control verifies category assignment Document Control assigns next available sequence number Number recorded in Document Master List Author creates document using assigned number Validation: Number format matches standard; no duplicates in Master List
Change TypeRevision IncrementExampleMajor revisionIncrement numberRev 01 โ Rev 02Minor revisionIncrement sub-revisionRev 01 โ Rev 01.1AdministrativeNo change or letter suffixRev 01 โ Rev 01a See references/document-control-procedures.md for complete numbering guidance.
Obtain required reviews and approvals before document release.
Author completes document draft Author submits for review via routing form or DMS Reviewers assigned based on document type Reviewers provide comments within review period (5-10 business days) Author addresses comments and documents responses Author resubmits revised document Approvers sign and date Validation: All required reviewers completed; all comments addressed with documented disposition
DispositionAction RequiredAcceptIncorporate comment as writtenAccept with modificationIncorporate with changes, document rationaleRejectDo not incorporate, document justificationDeferAddress in future revision, document reason
Document Level 1 (Policy/QM): CEO or delegate + QA Manager Document Level 2 (SOP): Department Manager + QA Manager Document Level 3 (WI/TF): Area Supervisor + QA Representative
ElementRequirementNamePrinted name of signerSignatureHandwritten or electronic signatureDateDate signature appliedRoleFunction/role of signer
Manage document changes systematically through review and approval.
Identify need for document change Complete Change Request Form with justification Document Control assigns change number and logs request Route to reviewers for impact assessment Obtain approvals based on change classification Author implements approved changes Update revision number and change history Validation: Changes match approved scope; change history complete
ClassDefinitionApproval LevelExamplesAdministrativeNo content impactDocument ControlTypos, formattingMinorLimited content changeProcess Owner + QAClarificationsMajorSignificant content changeFull review cycleNew requirementsEmergencyUrgent safety/complianceExpedited + retrospectiveSafety issues
Impact AreaAssessment QuestionsTrainingDoes change require retraining?EquipmentDoes change affect equipment or systems?ValidationDoes change require revalidation?RegulatoryDoes change affect regulatory filings?Other DocumentsWhich related documents need updating?RecordsWhat records are affected?
Each document must include change history: | Revision | Date | Description | Author | Approver | |----------|------|-------------|--------|----------| | 01 | 2023-01-15 | Initial release | J. Smith | M. Jones | | 02 | 2024-03-01 | Updated workflow | J. Smith | M. Jones |
Implement electronic record and signature controls for FDA compliance.
Applies ToDoes Not Apply ToRecords required by FDA regulationsPaper recordsRecords submitted to FDAInternal non-regulated documentsElectronic signatures on required recordsGeneral email communication
Validate system for accuracy and reliability Implement secure audit trail for all changes Restrict system access to authorized individuals Generate accurate copies in human-readable format Protect records throughout retention period Validation: Audit trail captures who, what, when for all changes
RequirementImplementationSecureCannot be modified by usersComputer-generatedSystem creates automaticallyTime-stampedDate and time of each actionOriginal valuesPrevious values retainedUser identityWho made each change
RequirementImplementationUnique to individualNot shared between personsAt least 2 componentsUser ID + password minimumSignature manifestationName, date/time, meaning displayedLinked to recordCannot be excised or copied
Every electronic signature must display: ElementExamplePrinted nameJohn SmithDate and time2024-03-15 14:32:05 ESTMeaningApproved for Release
Access Controls: Unique user ID for each person Password complexity enforced Account lockout after failed attempts Session timeout after inactivity Audit Trail: All record creation logged All modifications logged with old/new values User identity captured Date/time stamp on all entries Security: Role-based access control Encryption for data at rest and in transit Regular backup and tested recovery See references/21cfr11-compliance-guide.md for detailed compliance requirements.
references/document-control-procedures.md contains: Document numbering system and format Document lifecycle stages and transitions Review and approval workflow details Change control process with classification criteria Distribution and access control methods Record retention periods and disposal procedures Document Master List requirements
references/21cfr11-compliance-guide.md contains: Part 11 scope and applicability Electronic record requirements (ยง11.10) Electronic signature requirements (ยง11.50, 11.100, 11.200) System control specifications Validation approach and documentation Compliance checklist and gap assessment template Common FDA deficiencies and prevention
# Validate document metadata python scripts/document_validator.py --doc document.json # Interactive validation mode python scripts/document_validator.py --interactive # JSON output for integration python scripts/document_validator.py --doc document.json --output json # Generate sample document JSON python scripts/document_validator.py --sample > sample_doc.json Validates: Document numbering convention compliance Title and status requirements Date validation (effective, review due) Approval requirements by document type Change history completeness 21 CFR Part 11 controls (audit trail, signatures)
{ "number": "SOP-02-001", "title": "Document Control Procedure", "doc_type": "SOP", "revision": "03", "status": "Effective", "effective_date": "2024-01-15", "review_date": "2025-01-15", "author": "J. Smith", "approver": "M. Jones", "change_history": [ {"revision": "01", "date": "2022-01-01", "description": "Initial release"}, {"revision": "02", "date": "2023-01-15", "description": "Updated workflow"}, {"revision": "03", "date": "2024-01-15", "description": "Added e-signature requirements"} ], "has_audit_trail": true, "has_electronic_signature": true, "signature_components": 2 }
Track document control system performance.
MetricTargetCalculationDocument cycle time<30 daysAverage days from draft to effectiveReview completion rate>95%Reviews completed on time / Total reviewsChange request backlog<10Open change requests at month endOverdue review rate<5%Documents past review date / Total effectiveAudit finding rate<2 per auditDocument control findings per internal audit
Document TypeReview FrequencyPolicyEvery 3 yearsSOPEvery 2 yearsWIEvery 2 yearsSpecificationsAs needed or with product changesForms/TemplatesEvery 3 years
Sub-clauseRequirement4.2.1Quality management system documentation4.2.2Quality manual4.2.3Medical device file (technical documentation)4.2.4Control of documents4.2.5Control of records
SectionRequirement820.40Document controls820.180General record requirements820.181Device master record820.184Device history record820.186Quality system record
FindingPreventionObsolete documents in useImplement distribution controlMissing approval signaturesEnforce workflow before releaseIncomplete change historyRequire history update with each revisionNo periodic review scheduleEstablish and enforce review calendarInadequate audit trailValidate DMS for Part 11 compliance
Writing, remixing, publishing, visual generation, and marketing content production.
Largest current source with strong distribution and engagement signals.