clinical-trial-protocol-waypoint-based-design
Sub-skill of clinical-trial-protocol: Waypoint-Based Design (+2).
Best use case
clinical-trial-protocol-waypoint-based-design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of clinical-trial-protocol: Waypoint-Based Design (+2).
Teams using clinical-trial-protocol-waypoint-based-design 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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/waypoint-based-design/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clinical-trial-protocol-waypoint-based-design Compares
| Feature / Agent | clinical-trial-protocol-waypoint-based-design | 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: Waypoint-Based Design (+2).
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
# Waypoint-Based Design (+2) ## Waypoint-Based Design All analysis data is stored in `waypoints/` directory as JSON/markdown files: ``` waypoints/ ├── intervention_metadata.json # Intervention info, status, initial context ├── 01_clinical_research_summary.json # Similar trials, FDA guidance, recommendations ├── 02_protocol_foundation.md # Protocol sections 1-6 (Step 2) ├── 03_protocol_intervention.md # Protocol sections 7-8 (Step 3) ├── 04_protocol_operations.md # Protocol sections 9-12 (Step 4) ├── 02_protocol_draft.md # Complete protocol (concatenated in Step 4) ├── 02_protocol_metadata.json # Protocol metadata └── 02_sample_size_calculation.json # Statistical sample size calculation ``` **Rich Initial Context Support:** Users can provide substantial documentation, technical specifications, or research data when initializing the intervention (Step 0). This is preserved in `intervention_metadata.json` under the `initial_context` field. Later steps reference this context for more informed protocol development. ## Modular Subskill Steps Each step is an independent skill in `references/` directory: ``` references/ ├── 00-initialize-intervention.md # Collect device or drug information ├── 01-research-protocols.md # Clinical trials research and FDA guidance ├── 02-protocol-foundation.md # Protocol sections 1-6 (foundation, design, population) ├── 03-protocol-intervention.md # Protocol sections 7-8 (intervention details) ├── 04-protocol-operations.md # Protocol sections 9-12 (assessments, statistics, operations) └── 05-generate-document.md # NIH Protocol generation ``` ## Utility Scripts ``` scripts/ └── sample_size_calculator.py # Statistical power analysis (validated) ```
Related Skills
wave-based-parallel-plan-execution
Orchestrate phase execution by discovering dependencies, grouping into waves, spawning subagents, and collecting results with optional wave filtering
batch-syntax-fix-with-regex-line-based-fallback
Fix repeated syntax errors across many files using regex, then fall back to line-based parsing when regex fails
interactive-Codex-to-file-based-fallback
Switch from tmux/interactive Codex to file-based Codex -p execution when interactive runs fail with upstream errors or analysis-only stalls, then verify landing from git/GitHub state.
itinerary-design
Use when constructing a day-by-day itinerary inside a trip plan. Encodes base-count rules, jet-lag handling, transit-day discipline, slack budgeting, and the "last day = travel only" rule. Invoked by the trip-planner skill.
clinical-trial-protocol
Generate clinical trial protocols for medical devices or drugs through a modular, waypoint-based architecture with research-only and full protocol modes.
mooring-design
Design and analyze mooring systems including CALM and SALM buoys, catenary moorings, and spread mooring configurations. Covers mooring line design, safety factors, environmental loading, and compliance with DNV, API, and ABS standards.
touchdesigner-mcp
Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.
popular-web-designs
54 production-quality design systems extracted from real websites. Load a template to generate HTML/CSS that matches the visual identity of sites like Stripe, Linear, Vercel, Notion, Airbnb, and more. Each template includes colors, typography, components, layout rules, and ready-to-use CSS values.
design-md
Author/validate/export Google's DESIGN.md token spec files.
Codex-design
Design one-off HTML artifacts (landing, deck, prototype).
worker-discovery-protocol
Protocol for workers to capture and propagate discoveries back to the orchestrator and shared knowledge base. Phase 3 of orchestrator/worker context enforcement (#2020).
frontend-design
Create distinctive, production-grade web interfaces with high design quality. Use for components, pages, dashboards, and full applications that need to stand out from generic AI aesthetics.