LLMs-Universal-Life-Science-and-Clinical-Skills- regulatory-drafter

<!--

install
source · Clone the upstream repo
git clone https://github.com/mdbabumiamssm/LLMs-Universal-Life-Science-and-Clinical-Skills-
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/mdbabumiamssm/LLMs-Universal-Life-Science-and-Clinical-Skills- "$T" && mkdir -p ~/.claude/skills && cp -r "$T/Skills/External_Collections/Antigravity_Skills/regulatory-drafter" ~/.claude/skills/mdbabumiamssm-llms-universal-life-science-and-clinical-skills-regulatory-drafter && rm -rf "$T"
manifest: Skills/External_Collections/Antigravity_Skills/regulatory-drafter/SKILL.md
source content
<!-- # COPYRIGHT NOTICE # This file is part of the "Universal Biomedical Skills" project. # Copyright (c) 2026 MD BABU MIA, PhD <md.babu.mia@mssm.edu> # All Rights Reserved. # # This code is proprietary and confidential. # Unauthorized copying of this file, via any medium is strictly prohibited. # # Provenance: Authenticated by MD BABU MIA -->

name: 'regulatory-drafter' description: 'Drafts regulatory documents (FDA, EMA) with audit trails and specific "Thinking Block" reasoning. Use for high-stakes compliance writing.' measurable_outcome: Execute skill workflow successfully with valid output within 15 minutes. allowed-tools:

  • read_file
  • run_shell_command

Regulatory Document Drafter

This skill generates compliant drafts for regulatory submissions, emphasizing auditability and adherence to guidelines (ICH, FDA).

When to use this skill

  • When asked to write sections of an IND, NDA, or CSR (Clinical Study Report).
  • When responding to "Request for Information" (RFI) from health authorities.
  • When the user requires "reasoning" or "thinking" to be visible (Anthropic style).

How to use it

  1. Analyze Context:
    • Identify the specific regulatory document type (e.g., "Module 2.5 Clinical Overview").
    • Retrieve relevant guidelines (e.g., "FDA Draft Guidance on X").
  2. Thinking Block (Internal Monologue):
    • Before writing, outline the strategy in a
      <thinking>
      block.
    • Assess potential risks or claims that require citation.
  3. Drafting:
    • Use formal, objective regulatory language (e.g., "The data suggest..." instead of "We proved...").
    • Insert placeholders for data references
      [Link to Table 14.2.1]
      .
  4. Audit Trail:
    • Append a "Compliance Check" section listing which guidelines were consulted.
<!-- AUTHOR_SIGNATURE: 9a7f3c2e-MD-BABU-MIA-2026-MSSM-SECURE -->