sap-critic

Audit clinical trial statistical analysis plans for ICH E9 and E9(R1) compliance.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/zivtech/joyus-desktop --skill sap-critic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sap-critic
Source: https://github.com/zivtech/joyus-desktop/tree/main/.claude/skills/sap-critic
Command: npx skills add https://github.com/zivtech/joyus-desktop --skill sap-critic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents research integrity failures by identifying vague language, missing data strategy gaps, and post-hoc flexibility in Statistical Analysis Plans (SAPs) before database lock.

Core Features & Use Cases

  • Structural Audit: Systematically verifies all 12 ICH E9 required elements for clinical trial documentation.
  • Estimand Framework Assessment: Validates alignment with ICH E9(R1) standards, ensuring intercurrent events and population summaries are clearly defined.
  • Pre-specification Rigor: Distinguishes between legitimate confirmatory analysis and post-hoc data-driven decisions that threaten trial validity.

Quick Start

Use the sap-critic skill to perform a full pre-lock audit on the attached statistical analysis plan document.

Frequently Asked Questions about sap-critic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a clinical trial statistical analysis plan before database lock?

You can audit a clinical trial statistical analysis plan by systematically verifying all 12 ICH E9 required elements and evaluating estimand definitions against ICH E9(R1) standards. This structured review identifies missing data strategies and multiplicity control gaps before database lock.

What is estimand framework alignment in clinical trials?

Estimand framework alignment validates that a clinical trial SAP clearly defines intercurrent events and population summaries according to ICH E9(R1) standards. It ensures treatment effects are precisely specified, preventing ambiguous data interpretation during regulatory submission.

How do I check pre-specification rigor and prevent post-hoc bias in a SAP?

Checking pre-specification rigor involves distinguishing between legitimate confirmatory analysis and post-hoc data-driven decisions within the SAP. This process targets vague language and identifies flexibility that threatens trial validity and research integrity before database lock.

Can I use an automated audit for ICH E9 regulatory compliance on my SAP document?

Yes, you can perform a full regulatory compliance audit on an attached statistical analysis plan document. The audit evaluates adherence to ICH E9 and ICH E9(R1) standards, providing a structured verdict on trial integrity and identifying critical regulatory gaps.

What are the most common missing data strategy gaps in clinical trial SAPs?

Common missing data strategy gaps include failing to clearly define intercurrent events and lacking precise estimand definitions under ICH E9(R1). A structured pre-lock audit identifies these specific gaps in missing data handling and multiplicity control before regulatory submission.

When should I not use an automated SAP audit approach?

You should not rely solely on an automated SAP audit after database lock has occurred, as it specifically targets pre-specification rigor to prevent post-hoc bias. It functions as a pre-lock verification step rather than a post-hoc data analysis tool.