Clinical Trial Protocol Drafting
When to use this skill
- Draft protocol sections from a grant document or study synopsis
- Generate objectives, background/rationale, or study design sections
- Ensure protocol language complies with ICH E6(R2), E8(R1), E9
- Check regulatory requirements from 21 CFR Part 312 for IND protocols
- Assemble multiple sections into a cohesive protocol document
MCP Dependencies
| MCP Server |
Tool |
Purpose |
| fda-ecfr |
get_cfr_section |
Retrieve 21 CFR regulatory text |
| fda-ecfr |
search_cfr |
Search across CFR titles |
| awslabs.bedrock-kb-retrieval-mcp-server |
retrieve |
Query ICH E6/E8/E9 content via Bedrock Knowledge Base |
The fda-ecfr server is in mcp-servers/agentcore-gateway/fda-ecfr/ — deploy it first.
For ICH guidelines, set up a Bedrock Knowledge Base per references/ich-knowledge-base-setup.md and use the existing awslabs bedrock-kb-retrieval-mcp-server.
Workflow: Protocol Drafting from Grant Document
Step 1: Objectives Section
Generate the draft Objectives section of a clinical trial protocol.
- Extract from the grant: specific aims, primary endpoint, secondary endpoints.
- Use
retrieve with query "protocol objectives requirements ICH E6(R2) Section 6" to retrieve guidance on how protocol objectives should be stated.
Output structure:
- Primary Objective (linked to the primary endpoint)
- Secondary Objectives (linked to each secondary endpoint)
- Exploratory Objectives (if any are implied by the grant aims)
Each objective: clear, measurable, single-sentence statement following ICH conventions. Map each objective to its corresponding endpoint.
Step 2: Background & Rationale Section
Generate the draft Background and Rationale section.
- Extract from the grant: disease context, preliminary data (preclinical and Phase 1 results), unmet medical need, scientific rationale for the investigational agent.
- Use
get_cfr_section with part "312" and section "23" to retrieve 21 CFR 312.23 requirements on nonclinical and clinical background information for an IND protocol.
- Use
retrieve with query "protocol background section requirements ICH E6(R2) E8(R1)" to retrieve guidance.
Output structure:
- Disease Overview (epidemiology, molecular subtype prevalence, current standard of care)
- Unmet Medical Need (limitations of existing therapies)
- Investigational Agent Summary (mechanism of action, selectivity profile)
- Relevant Nonclinical Findings (IC50 data, selectivity over wild-type)
- Clinical Experience to Date (Phase 1 dose-escalation results, RP2D, preliminary efficacy and safety signals)
- Study Rationale (why this agent, this population, this design)
Tone: scientific, appropriate for IRB submission. Cite grant preliminary data where applicable.
Step 3: Study Design Section
Generate the draft Study Design section.
- Extract from the grant: study design type, randomization scheme, treatment arms, dosing, sample size, study duration, number of sites, target population.
- Use
retrieve with query "general study design considerations randomization ICH E8(R1)" for design guidance.
- Use
retrieve with query "statistical design principles sample size ICH E9" for statistical principles.
- Use
get_cfr_section with part "312" and section "23" for 21 CFR 312.23(a)(6) requirements on protocol design elements.
Output structure:
- Overall Design (phase, randomization ratio, open-label justification, multicenter)
- Treatment Arms (experimental arm with dose/schedule, control arm with regimen options)
- Study Schema (text-based visual flow: screening → randomization → treatment → follow-up)
- Randomization and Stratification (method, stratification factors if applicable)
- Sample Size Justification (statistical basis, power, expected effect size)
- Study Duration (enrollment period, treatment duration, follow-up period)
Step 4: Assembly
Assemble all drafted sections into a single cohesive protocol document.
Formatting:
- Protocol title page (study title, PI, funding source, protocol version/date)
- Sequential section numbering
- Consistent formatting, tense, and terminology
- Table of Contents
- Cross-reference harmonization (objectives referenced in study design)
- Flag inconsistencies as reviewer comments
Do not alter scientific content. Only harmonize language and ensure smooth transitions.
Conventions
- Lead with the most clinically relevant information in each section
- Use ICH-compliant terminology throughout (e.g., "investigational medicinal product" not "drug")
- Distinguish primary from secondary objectives clearly
- Include regulatory citations inline (e.g., "per 21 CFR 312.23(a)(6)")
- For VUS or uncertain data: note limitations and recommend additional review
- Never fabricate clinical data — use only what is provided in the source document
- Flag sections where the grant provides insufficient detail for protocol-level specificity
Regulatory References
- ICH E6(R2): Good Clinical Practice, Integrated Addendum
- ICH E8(R1): General Considerations for Clinical Studies
- ICH E9: Statistical Principles for Clinical Trials
- 21 CFR Part 312: Investigational New Drug Application
- 21 CFR Part 50: Protection of Human Subjects
- 21 CFR Part 56: Institutional Review Boards
1---2name: clinical-protocol-drafting3description: Use when drafting clinical trial protocol sections (objectives, background, study design) grounded in ICH guidelines (E6, E8, E9) and FDA regulations (21 CFR Part 312). Generates IRB-ready protocol documents from grant documents or study synopses.4---56# Clinical Trial Protocol Drafting78## When to use this skill910- Draft protocol sections from a grant document or study synopsis11- Generate objectives, background/rationale, or study design sections12- Ensure protocol language complies with ICH E6(R2), E8(R1), E913- Check regulatory requirements from 21 CFR Part 312 for IND protocols14- Assemble multiple sections into a cohesive protocol document1516## MCP Dependencies1718| MCP Server | Tool | Purpose |19|---|---|---|20| fda-ecfr | `get_cfr_section` | Retrieve 21 CFR regulatory text |21| fda-ecfr | `search_cfr` | Search across CFR titles |22| awslabs.bedrock-kb-retrieval-mcp-server | `retrieve` | Query ICH E6/E8/E9 content via Bedrock Knowledge Base |2324The fda-ecfr server is in `mcp-servers/agentcore-gateway/fda-ecfr/` — deploy it first.25For ICH guidelines, set up a Bedrock Knowledge Base per `references/ich-knowledge-base-setup.md` and use the existing awslabs bedrock-kb-retrieval-mcp-server.2627## Workflow: Protocol Drafting from Grant Document2829### Step 1: Objectives Section3031Generate the draft Objectives section of a clinical trial protocol.32331. Extract from the grant: specific aims, primary endpoint, secondary endpoints.342. Use `retrieve` with query "protocol objectives requirements ICH E6(R2) Section 6" to retrieve guidance on how protocol objectives should be stated.3536**Output structure:**37- Primary Objective (linked to the primary endpoint)38- Secondary Objectives (linked to each secondary endpoint)39- Exploratory Objectives (if any are implied by the grant aims)4041Each objective: clear, measurable, single-sentence statement following ICH conventions. Map each objective to its corresponding endpoint.4243### Step 2: Background & Rationale Section4445Generate the draft Background and Rationale section.46471. Extract from the grant: disease context, preliminary data (preclinical and Phase 1 results), unmet medical need, scientific rationale for the investigational agent.482. Use `get_cfr_section` with part "312" and section "23" to retrieve 21 CFR 312.23 requirements on nonclinical and clinical background information for an IND protocol.493. Use `retrieve` with query "protocol background section requirements ICH E6(R2) E8(R1)" to retrieve guidance.5051**Output structure:**52- Disease Overview (epidemiology, molecular subtype prevalence, current standard of care)53- Unmet Medical Need (limitations of existing therapies)54- Investigational Agent Summary (mechanism of action, selectivity profile)55- Relevant Nonclinical Findings (IC50 data, selectivity over wild-type)56- Clinical Experience to Date (Phase 1 dose-escalation results, RP2D, preliminary efficacy and safety signals)57- Study Rationale (why this agent, this population, this design)5859Tone: scientific, appropriate for IRB submission. Cite grant preliminary data where applicable.6061### Step 3: Study Design Section6263Generate the draft Study Design section.64651. Extract from the grant: study design type, randomization scheme, treatment arms, dosing, sample size, study duration, number of sites, target population.662. Use `retrieve` with query "general study design considerations randomization ICH E8(R1)" for design guidance.673. Use `retrieve` with query "statistical design principles sample size ICH E9" for statistical principles.684. Use `get_cfr_section` with part "312" and section "23" for 21 CFR 312.23(a)(6) requirements on protocol design elements.6970**Output structure:**71- Overall Design (phase, randomization ratio, open-label justification, multicenter)72- Treatment Arms (experimental arm with dose/schedule, control arm with regimen options)73- Study Schema (text-based visual flow: screening → randomization → treatment → follow-up)74- Randomization and Stratification (method, stratification factors if applicable)75- Sample Size Justification (statistical basis, power, expected effect size)76- Study Duration (enrollment period, treatment duration, follow-up period)7778### Step 4: Assembly7980Assemble all drafted sections into a single cohesive protocol document.8182**Formatting:**83- Protocol title page (study title, PI, funding source, protocol version/date)84- Sequential section numbering85- Consistent formatting, tense, and terminology86- Table of Contents87- Cross-reference harmonization (objectives referenced in study design)88- Flag inconsistencies as reviewer comments8990Do not alter scientific content. Only harmonize language and ensure smooth transitions.9192## Conventions9394- Lead with the most clinically relevant information in each section95- Use ICH-compliant terminology throughout (e.g., "investigational medicinal product" not "drug")96- Distinguish primary from secondary objectives clearly97- Include regulatory citations inline (e.g., "per 21 CFR 312.23(a)(6)")98- For VUS or uncertain data: note limitations and recommend additional review99- Never fabricate clinical data — use only what is provided in the source document100- Flag sections where the grant provides insufficient detail for protocol-level specificity101102## Regulatory References103104- ICH E6(R2): Good Clinical Practice, Integrated Addendum105- ICH E8(R1): General Considerations for Clinical Studies106- ICH E9: Statistical Principles for Clinical Trials107- 21 CFR Part 312: Investigational New Drug Application108- 21 CFR Part 50: Protection of Human Subjects109- 21 CFR Part 56: Institutional Review Boards