Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
borghei avatar

Quality Documentation Manager

  • 132 installs
  • 451 repo stars
  • Updated July 21, 2026
  • borghei/claude-skills

Create and maintain quality-focused documentation: test plans, acceptance criteria, traceability matrices, and release notes tied to verification evidence.

About

quality-documentation-manager helps Claude produce and refine quality-centric docs during build: test strategies, traceability from requirements to cases, defect and sign-off records, and polished release notes aligned with verification standards.

  • Test plan and case authoring
  • Acceptance criteria traceability
  • QA evidence and sign-off docs
  • Release note preparation
  • Documentation consistency reviews

Quality Documentation Manager by the numbers

  • 132 all-time installs (skills.sh)
  • Ranked #599 of 1,879 Documentation skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/borghei/claude-skills --skill quality-documentation-manager

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs132
repo stars451
Last updatedJuly 21, 2026
Repositoryborghei/claude-skills

What it does

Create and maintain quality-focused documentation: test plans, acceptance criteria, traceability matrices, and release notes tied to verification evidence.

Files

SKILL.mdMarkdownGitHub ↗

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)

Related skills

Documentationdocstesting

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.