documentation-generation

Generate technical and compliance documentation for EDC systems in clinical trials.

1|1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/nroze22/TalosixSkills --skill documentation-generation-nroze22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-generation
Source: https://github.com/nroze22/TalosixSkills/tree/main/.claude/skills/documentation-generation
Command: npx skills add https://github.com/nroze22/TalosixSkills --skill documentation-generation-nroze22

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of essential technical and compliance documentation for Electronic Data Capture (EDC) systems used in clinical trials, addressing critical regulatory requirements and reducing manual effort.

Core Features & Use Cases

  • API Documentation: Generates detailed documentation for API endpoints, including request/response schemas, authentication, and EDC-specific concerns like PHI and electronic signatures.
  • Architecture Documentation: Maps system components, data flows, and technology stacks.
  • Runbooks: Creates step-by-step operational procedures for common tasks and incident response.
  • Compliance Documentation: Generates IQ/OQ/PQ documentation and traceability matrices to meet regulatory standards (21 CFR Part 11, ICH E6(R2), GAMP 5).
  • Use Case: A new EDC feature requires comprehensive API documentation and an IQ/OQ/PQ package for regulatory submission. This Skill can generate these artifacts by analyzing the codebase and configurations.

Quick Start

Generate API documentation for the codebase, focusing on endpoints handling Protected Health Information.

Frequently Asked Questions about documentation-generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate IQ OQ PQ documentation for an EDC system in clinical trials?

Generating GxP compliance documentation for clinical trials requires mapping system components and test results to regulatory standards like 21 CFR Part 11 and ICH E6(R2). It ensures your Electronic Data Capture system meets audit requirements through automated traceability matrices and qualification protocols.

What is the best way to create API documentation for EDC endpoints handling Protected Health Information?

Creating API documentation for EDC endpoints handling PHI requires detailing request/response schemas, authentication mechanisms, and electronic signature workflows. This ensures your API documentation satisfies clinical trial regulatory compliance and data protection requirements.

Can I automate 21 CFR Part 11 compliance documentation from my existing codebase?

Automating 21 CFR Part 11 compliance documentation from a codebase is possible by analyzing source code, configurations, and test results. This produces traceability matrices and qualification protocols required for regulatory submission of Electronic Data Capture systems.

How do I write operational runbooks for clinical trial EDC system incidents?

Writing operational runbooks for EDC system incidents involves mapping system architecture and data flows to create step-by-step procedures. This defines incident response protocols and common operational tasks for clinical trial data capture systems.

Does this approach to EDC documentation support GAMP 5 and ICH E6(R2) standards?

EDC documentation generation supports GAMP 5 and ICH E6(R2) standards by producing compliance artifacts including IQ/OQ/PQ packages and traceability matrices. It analyzes technical implementations to verify adherence to these clinical trial regulatory frameworks.