clinical-trial-protocol-implementation-requirements

Sub-skill of clinical-trial-protocol: Implementation Requirements.

5 stars

Best use case

clinical-trial-protocol-implementation-requirements is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of clinical-trial-protocol: Implementation Requirements.

Teams using clinical-trial-protocol-implementation-requirements should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/implementation-requirements/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/science/bio-research/clinical-trial-protocol/implementation-requirements/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/implementation-requirements/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How clinical-trial-protocol-implementation-requirements Compares

Feature / Agent	clinical-trial-protocol-implementation-requirements	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Sub-skill of clinical-trial-protocol: Implementation Requirements.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Implementation Requirements

## Implementation Requirements


When this skill is invoked:

1. **Display the welcome message with mode selection** (shown in "Startup: Welcome and Mode Selection" section)

2. **Wait for user mode selection** (1: Research Only, 2: Full Protocol, 3: Exit)

3. **Execute based on selected mode:**
   - **Research Only Mode (Option 1):**
     - Execute Research Only Workflow Logic (Steps 0-1 only)
     - Generate formatted research summary as .md artifact
     - Offer option to continue with full protocol or exit
   - **Full Protocol Mode (Option 2):**
     - Execute Full Workflow Logic (Steps 0-5)
     - Check for existing waypoints and resume from last completed step
     - OR start from Step 0 if no waypoints exist
     - Execute all steps sequentially until complete

4. **For each step execution (LAZY LOADING - On-Demand Only):**
   - **ONLY when a step is ready to execute**, read the corresponding subskill file
   - Do NOT read subskill files in advance or "to prepare"
   - Example: When Step 1 needs to run, THEN read `references/01-research-protocols.md` and follow its instructions
   - **For protocol development:** Execute Steps 2, 3, 4 sequentially in order
   - Do NOT try to execute multiple steps in parallel - run sequentially
   - Read each step's subskill file only when that specific step is about to execute

5. **Research summary artifact generation (Research Only Mode):**
   - After Step 1 completes, read waypoint files
   - Generate comprehensive, well-formatted markdown summary
   - Save to `waypoints/research_summary.md`
   - Display completion message with key findings

6. **Handle errors gracefully:**
   - If a step fails, give user option to retry or exit
   - If MCP server unavailable, explain how to install
   - All progress is saved automatically in waypoints

7. **Track progress:**
   - Update `waypoints/intervention_metadata.json` after each step
   - Show progress indicators to user (e.g., "Progress: 3/6 steps complete" or "Progress: 2/2 research steps complete")
   - Provide clear feedback on what's happening

8. **Final output:**
   - **Research Only:** Display research summary location and offer to continue with full protocol
   - **Full Protocol:** Congratulate user, display protocol location and next steps
   - Remind user of disclaimers

Related Skills

read-only-pre-implementation-audit

from vamseeachanta/workspace-hub

Systematic cross-check workflow to validate assumptions before TDD coding begins

portable-baseline-pattern-implementation

from vamseeachanta/workspace-hub

Implement portable configuration baselines by separating machine-agnostic settings from machine-specific hooks and plugins

plan-gated-issue-implementation

from vamseeachanta/workspace-hub

Workflow for executing pre-approved GitHub issues with mandatory validation checkpoints

live-state-aware-overnight-implementation-prompts

from vamseeachanta/workspace-hub

Design overnight implementation prompts that begin with a live repo/CI precheck so workers continue from partial progress instead of replaying stale handoffs.

clinical-trial-protocol

from vamseeachanta/workspace-hub

Generate clinical trial protocols for medical devices or drugs through a modular, waypoint-based architecture with research-only and full protocol modes.

worker-discovery-protocol

from vamseeachanta/workspace-hub

Protocol for workers to capture and propagate discoveries back to the orchestrator and shared knowledge base. Phase 3 of orchestrator/worker context enforcement (#2020).