assess-development-plan-gaps
SolidAssesses a clinical pharmacology development plan against guidance-anchored evidence expectations, classifying every expected element as present, triggered, waivable-with-rationale, or a residual gap, each traced to the criterion that creates the obligation. Use this skill when someone asks what clinical pharmacology evidence a programme is still missing, whether a plan covers what a reviewer will expect, or which studies the drug's own properties have made obligatory — for example "what CP work are we still missing before the pre-NDA meeting" or "does this plan cover the renal and hepatic expectations". Do not use for reviewing one interaction package, for assembling agency-facing briefing content, or for any request to decide whether a gap is acceptable, to commit to a study, or to approve a plan.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- malekokour
- Repository
- malekokour/clinpharm-pmx-skills
- Created
- 1 weeks ago
- Last Updated
- 6 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
assess-pharmacogenomic-evidence
Assesses whether pharmacogenomic covariate effects are characterised across the programme's evidence base — in-vitro enzyme and transporter genotype data, PopPK covariate analyses, dedicated PGx sub-studies, and the labelling concept — producing a gene-enzyme-phenotype register in which every stated PGx effect traces to its source and every source-identified polymorphism traces to its downstream statement. Use this skill when someone asks whether pharmacogenomic effects are characterised for a compound, whether a PopPK analysis covers the relevant polymorphisms, or what PGx gaps remain. Example: "Please pharmacogenomic effects are characterised for a compound." Do not use for demographic covariates (age, sex, body size), for organ-impairment characterisation, for drug-drug interaction assessment, or for any request to recommend a genotype-based dose adjustment.
prepare-briefing-package-content
Drafts and reviews the clinical pharmacology portion of a regulatory briefing package — answerable questions to the agency, applicant positions with their supporting evidence, and validated annex cross-references — aligned to the public structure of clinical pharmacology review. Use this skill when someone asks to draft, structure, stress-test or QC the CP content of a briefing book or meeting package — for example "draft the clin pharm section of our pre-NDA briefing package", "which questions should we ask", or "check every position in this package is actually supported". Do not use for responding to questions an agency has already sent, for writing the meeting request itself, for CTD summary or labelling content, or for any request to decide whether a position will be accepted.
assess-special-population-strategy
Assesses the completeness and internal consistency of a programme's special-population evidence strategy — renal impairment, hepatic impairment, paediatrics, pregnancy and lactation, elderly, and other defined sub-populations — against the programme's declared scope, the target product profile, and the guidance-anchored criteria that create study or analysis obligations for each population. Use this skill when someone asks whether the special-population strategy covers what a reviewer will expect, which populations still need characterisation, or whether the strategy documents are internally consistent. Example: "Please the special-population strategy covers what a reviewer will expect, which populations still need characterisation." Do not use for reviewing one organ-impairment study report, for demographic covariate assessment in a PopPK, for pharmacogenomic characterisation, or for any request to decide whether a waiver rationale is sufficient or to commit to a study.