clinical-trial-protocol-execution-control-read-this-first
Sub-skill of clinical-trial-protocol: EXECUTION CONTROL - READ THIS FIRST.
Best use case
clinical-trial-protocol-execution-control-read-this-first is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of clinical-trial-protocol: EXECUTION CONTROL - READ THIS FIRST.
Teams using clinical-trial-protocol-execution-control-read-this-first 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/execution-control-read-this-first/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clinical-trial-protocol-execution-control-read-this-first Compares
| Feature / Agent | clinical-trial-protocol-execution-control-read-this-first | 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: EXECUTION CONTROL - READ THIS FIRST.
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
# EXECUTION CONTROL - READ THIS FIRST ## EXECUTION CONTROL - READ THIS FIRST **CRITICAL: This orchestrator follows a SIMPLE START approach:** 1. **Display the welcome message FIRST** (shown in "Startup: Welcome and Confirmation" section below) 2. **Ask user to confirm they're ready to proceed** - Wait for confirmation (yes/no) 3. **Jump directly into Full Workflow Logic** - Automatically run subskills sequentially 4. **Do NOT pre-read subskill files** - Subskills are loaded on-demand only when their step executes **Why this matters:** - Pre-reading all subskills wastes context and memory - Subskills should only load when actually needed during execution - Workflow automatically handles resuming from existing waypoints
Related Skills
digitalmodel-worktree-test-execution-with-shared-venv
Run digitalmodel tests from isolated worktrees without uv editable-dependency failures by using the main repo's existing virtualenv and PYTHONPATH.
hermes-kanban-readability
Reapply the Hermes Kanban dashboard readability customizations (clickable bare URLs in card descriptions + readable card-text font, a visible horizontal scrollbar so all columns are reachable) as a user-override plugin that survives hermes-agent updates. Use when the Kanban board reverts to the Mondwest display font / plain-text Source URLs after a hermes update, or when bootstrapping a machine whose ~/.hermes was wiped.
worldenergydata-source-readiness
Route agents to the canonical worldenergydata source-readiness skill and summary script. Use when asked for worldenergydata data completeness, data locations, latest known data dates, scheduler freshness, source-readiness status, or acceptance-criteria inputs across the repo ecosystem.
plan-gated-issue-execution-wave
Execute a multi-issue architecture/planning wave in a plan-gated repo, then safely transition approved issues into implementation with file-based Codex prompts, local approval markers, subprocess monitoring, and cleanup handling for sandbox/hook edge cases.
orcawave-orcaflex-readiness-audit
Audit the real readiness of digitalmodel OrcaWave/OrcaFlex spec-driven workflows by reconciling workspace-hub issues, source/tests, semantic-equivalence boundaries, and wiki synthesis gaps.
work-around-merge-conflicts-in-test-execution
Run tests when repo has unresolved merge conflicts in config files by bypassing broken configs and executing tests directly
wave-based-parallel-plan-execution
Orchestrate phase execution by discovering dependencies, grouping into waves, spawning subagents, and collecting results with optional wave filtering
read-only-pre-implementation-audit
Systematic cross-check workflow to validate assumptions before TDD coding begins
plan-governance-vs-execution-boundary-for-adversarial-review
Keep stale-approval/governance remediation out of execution-path pseudocode, TDD, files-to-change, and deliverable acceptance when hardening a GitHub issue plan under adversarial review.
interactive-issue-execution-worktree-guardrails
Execute approved GitHub issues in isolated worktrees with interactive Codex/Codex runs, while containing agent drift and salvaging progress when provider/runtime problems occur.
gtm-site-readiness-audit-local-vs-production
Audit GTM feature work by separating local artifact readiness from production deployment state, then fix common blockers in aceengineer-website and GTM collateral.
gtm-prospect-pipeline-phased-execution
Phased execution pattern for