Token导航 LogoToken导航TokenDH.com
开发只读github未标认证来源可访问许可证需确认审计通过

quality-documentation-manager质量文件经理

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

2,305

周安装

98

GitHub Stars

103

下载量

808
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:quality-documentation-manager(质量文件经理)
来源仓库:https://github.com/borghei/claude-skills
仓库路径:skills/quality-documentation-manager
安装命令:
npx skills add https://github.com/borghei/claude-skills --skill quality-documentation-manager
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill quality-documentation-manager

简介

quality-documentation-manager 构建 ISO 13485 文档控制系统,涵盖编号规则、审批流程与电子记录合规。

  • 支持文档创建、评审、变更与废止全生命周期管理,满足 21 CFR Part 11 要求。
  • 输出模板库与流程图示例,加速质量体系文件标准化建设。
  • 实施前需确认组织现行文档实践,避免过度复杂化现有流程。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Quality Documentation Manager

Document control system design and management for ISO 13485-compliant quality management systems, including numbering conventions, approval workflows, change control, and electronic record compliance.


Table of Contents


Document Control Workflow

Implement document control from creation through obsolescence:

  1. Assign document number per numbering procedure
  2. Create document using controlled template
  3. Route for review to required reviewers
  4. Address review comments and document responses
  5. Obtain required approval signatures
  6. Assign effective date and distribute
  7. Update Document Master List
  8. Validation: Document accessible at point of use; obsolete versions removed

Document Lifecycle Stages

StageDefinitionActions Required
DraftUnder creation or revisionAuthor editing, not for use
ReviewCirculated for reviewReviewers provide feedback
ApprovedAll signatures obtainedReady for training/distribution
EffectiveTraining complete, releasedAvailable for use
SupersededReplaced by newer revisionRemove from active use
ObsoleteNo longer applicableArchive per retention schedule

Document Types and Prefixes

PrefixDocument TypeTypical Content
QMQuality ManualQMS overview, scope, policy
SOPStandard Operating ProcedureProcess-level procedures
WIWork InstructionTask-level step-by-step
TFTemplate/FormControlled forms
SPECSpecificationProduct/process specs
PLNPlanQuality/project plans

Required Reviewers by Document Type

Document TypeRequired ReviewersRequired Approvers
SOPProcess Owner, QAQA Manager, Process Owner
WIArea Supervisor, QAArea Manager
SPECEngineering, QAEngineering Manager, QA
TFProcess OwnerQA
Design DocumentsDesign Team, QADesign Control Authority

Document Numbering System

Assign consistent document numbers for identification and retrieval.

Numbering Format

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

Category Codes

CodeFunctional AreaDescription
01Quality ManagementQMS procedures, management review
02Document ControlThis area
03Human ResourcesTraining, competency
04Design & DevelopmentDesign control processes
05PurchasingSupplier management
06ProductionManufacturing procedures
07Quality ControlInspection, testing
08CAPACorrective/preventive actions
09Risk ManagementISO 14971 processes
10Regulatory AffairsSubmissions, compliance

Numbering Workflow

  1. Author requests document number from Document Control
  2. Document Control verifies category assignment
  3. Document Control assigns next available sequence number
  4. Number recorded in Document Master List
  5. Author creates document using assigned number
  6. Validation: Number format matches standard; no duplicates in Master List

Revision Designation

Change TypeRevision IncrementExample
Major revisionIncrement numberRev 01 → Rev 02
Minor revisionIncrement sub-revisionRev 01 → Rev 01.1
AdministrativeNo change or letter suffixRev 01 → Rev 01a

See references/document-control-procedures.md for complete numbering guidance.


Approval and Review Process

Obtain required reviews and approvals before document release.

Review Workflow

  1. Author completes document draft
  2. Author submits for review via routing form or DMS
  3. Reviewers assigned based on document type
  4. Reviewers provide comments within review period (5-10 business days)
  5. Author addresses comments and documents responses
  6. Author resubmits revised document
  7. Approvers sign and date
  8. Validation: All required reviewers completed; all comments addressed with documented disposition

Comment Disposition

DispositionAction Required
AcceptIncorporate comment as written
Accept with modificationIncorporate with changes, document rationale
RejectDo not incorporate, document justification
DeferAddress in future revision, document reason

Approval Matrix

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

Signature Requirements

ElementRequirement
NamePrinted name of signer
SignatureHandwritten or electronic signature
DateDate signature applied
RoleFunction/role of signer

Change Control Process

Manage document changes systematically through review and approval.

Change Control Workflow

  1. Identify need for document change
  2. Complete Change Request Form with justification
  3. Document Control assigns change number and logs request
  4. Route to reviewers for impact assessment
  5. Obtain approvals based on change classification
  6. Author implements approved changes
  7. Update revision number and change history
  8. Validation: Changes match approved scope; change history complete

Change Classification

ClassDefinitionApproval LevelExamples
AdministrativeNo content impactDocument ControlTypos, formatting
MinorLimited content changeProcess Owner + QAClarifications
MajorSignificant content changeFull review cycleNew requirements
EmergencyUrgent safety/complianceExpedited + retrospectiveSafety issues

Impact Assessment Checklist

Impact AreaAssessment Questions
TrainingDoes 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?

Change History Documentation

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 |

21 CFR Part 11 Compliance

Implement electronic record and signature controls for FDA compliance.

Part 11 Scope

Applies ToDoes Not Apply To
Records required by FDA regulationsPaper records
Records submitted to FDAInternal non-regulated documents
Electronic signatures on required recordsGeneral email communication

Electronic Record Controls

  1. Validate system for accuracy and reliability
  2. Implement secure audit trail for all changes
  3. Restrict system access to authorized individuals
  4. Generate accurate copies in human-readable format
  5. Protect records throughout retention period
  6. Validation: Audit trail captures who, what, when for all changes

Audit Trail Requirements

RequirementImplementation
SecureCannot be modified by users
Computer-generatedSystem creates automatically
Time-stampedDate and time of each action
Original valuesPrevious values retained
User identityWho made each change

Electronic Signature Requirements

RequirementImplementation
Unique to individualNot shared between persons
At least 2 componentsUser ID + password minimum
Signature manifestationName, date/time, meaning displayed
Linked to recordCannot be excised or copied

Signature Manifestation

Every electronic signature must display:

ElementExample
Printed nameJohn Smith
Date and time2024-03-15 14:32:05 EST
MeaningApproved for Release

System Controls Checklist

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.


Reference Documentation

Document Control Procedures

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

21 CFR Part 11 Compliance Guide

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

Tools

Document Validator

# 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)

Sample Document Input

{
  "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
}

Document Control Metrics

Track document control system performance.

Key Performance Indicators

MetricTargetCalculation
Document cycle time<30 daysAverage days from draft to effective
Review completion rate>95%Reviews completed on time / Total reviews
Change request backlog<10Open change requests at month end
Overdue review rate<5%Documents past review date / Total effective
Audit finding rate<2 per auditDocument control findings per internal audit

Periodic Review Schedule

Document TypeReview Frequency
PolicyEvery 3 years
SOPEvery 2 years
WIEvery 2 years
SpecificationsAs needed or with product changes
Forms/TemplatesEvery 3 years

Regulatory Requirements

ISO 13485:2016 Clause 4.2

Sub-clauseRequirement
4.2.1Quality management system documentation
4.2.2Quality manual
4.2.3Medical device file (technical documentation)
4.2.4Control of documents
4.2.5Control of records

FDA 21 CFR 820

SectionRequirement
820.40Document controls
820.180General record requirements
820.181Device master record
820.184Device history record
820.186Quality system record

Common Audit Findings

FindingPrevention
Obsolete documents in useImplement distribution control
Missing approval signaturesEnforce workflow before release
Incomplete change historyRequire history update with each revision
No periodic review scheduleEstablish and enforce review calendar
Inadequate audit trailValidate DMS for Part 11 compliance

Troubleshooting

ProblemLikely CauseResolution
Document validator reports "invalid numbering format"Document number does not match the PREFIX-CATEGORY-SEQUENCE patternEnsure the number follows the format SOP-02-001 (type prefix, 2-digit category code, 3-digit sequence). Check that the prefix matches a recognized document type (QM, SOP, WI, TF, SPEC, PLN).
Validation flags missing approver despite having signaturesapprover field is null or empty in the input JSONPopulate the approver field with the name of the approving authority. For SOPs, both Process Owner and QA Manager are required.
Review date validation fails for a current documentreview_date is in the pastUpdate the review date to reflect the next scheduled review. Documents past their review date should be flagged for periodic review and re-approval.
Change history marked incompleteNot all revisions have entries in the change_history arrayEvery revision increment must have a corresponding change history entry with revision number, date, description, and author. Fill gaps in the history.
Part 11 controls flagged despite using an eDMShas_audit_trail or has_electronic_signature set to falseSet both to true and ensure signature_components is at least 2 (user ID + password minimum per Part 11). Verify the eDMS produces computer-generated, timestamped audit trails.
Interactive mode does not display all validation rulesTerminal width too narrow for table outputWiden the terminal window or use --output json for structured output that is not affected by display width.
Obsolete documents still appearing as "Effective"Status field not updated during revision cycleWhen a new revision is released, update the prior revision's status to "Superseded" and ensure it is removed from points of use. Run the validator against the superseded document to confirm.

Success Criteria

  • Document numbering system enforced with zero duplicate numbers in the Document Master List and 100% format compliance
  • Document cycle time (draft to effective) averages less than 30 business days across all document types
  • Review completion rate exceeds 95% (reviews completed on time vs. total reviews initiated)
  • Overdue periodic review rate below 5% of total effective documents at any point
  • 21 CFR Part 11 compliance verified for all electronic records: audit trails capture who/what/when for every change, electronic signatures include printed name, date/time, and meaning
  • Change control process handles 100% of document changes through the classification workflow (Administrative/Minor/Major/Emergency) with documented impact assessments
  • Zero external audit findings related to document control in the most recent certification or surveillance audit

Scope & Limitations

In Scope:

  • Document numbering convention design and validation
  • Document lifecycle management (Draft through Obsolete)
  • Review and approval workflow enforcement
  • Change control process with classification and impact assessment
  • 21 CFR Part 11 electronic record and electronic signature compliance validation
  • Periodic review schedule management
  • Document Master List maintenance

Out of Scope:

  • eDMS software selection, implementation, or validation (the tool validates metadata, not the DMS platform itself)
  • EU Annex 11 computerized system validation (complementary to Part 11 but requires separate assessment approach)
  • Technical file / Design History File content creation (use regulatory-affairs-head for technical documentation)
  • Record retention schedule creation (the tool validates dates but does not determine regulatory retention periods)
  • Physical document distribution or archival logistics
  • Training record management (the tool validates training-related documents but does not manage training programs)

Integration Points

SkillIntegration
quality-manager-qms-iso13485Document control (Clause 4.2.3) and record control (Clause 4.2.4) are core QMS processes; the validator enforces ISO 13485 documentation requirements
qms-audit-expertInternal audits of Clause 4.2 verify document control effectiveness; audit findings drive document process improvements
quality-manager-qmrDocument control metrics (cycle time, overdue reviews, backlog) are reported to management review as QMS performance indicators
fda-consultant-specialistFDA QMSR (effective Feb 2026) incorporates ISO 13485 Clause 4.2 by reference; Part 11 compliance remains a separate FDA requirement for electronic records
capa-officerCAPA actions frequently require document revisions; the change control process tracks CAPA-driven document changes

Tool Reference

document_validator.py

Validates document metadata, numbering conventions, and regulatory control requirements.

FlagRequiredDescription
--docYes (or --interactive or --sample)Path to document metadata JSON file containing number, title, type, revision, status, dates, approvers, change history, and Part 11 fields
--interactiveNoLaunch interactive validation mode for guided document entry
--outputNoOutput format: json for structured output with severity-rated findings, omit for human-readable text
--sampleNoGenerate a sample document JSON template (pipe to file with > sample_doc.json)

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.5%
按下载量换算311

Claude

29.3%
按下载量换算237

Cursor

17.24%
按下载量换算139

Gemini CLI

10.29%
按下载量换算83

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills