prepare-position-defence-brief
SolidStructures a clinical pharmacology position defence brief — the evidence-backed argument for a CP position the team expects to defend before an agency. Maps the position statement to its evidence chain, identifies vulnerabilities, and assembles counter-arguments with sourced data. Use when preparing a CP position for agency discussion. Do not use for drafting the position itself, for deciding the position, or for predicting what an agency will accept.
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
prepare-assessment-aid-position
Structures the clinical pharmacology content of an assessment aid or applicant's position document — the tabulated summary an agency requests to facilitate their review. Extracts every CP claim, traces it to its source document, verifies internal consistency, and flags any position statement that crosses into a clinical or regulatory decision. Use when asked to prepare or review an assessment aid's CP section. Do not use for drafting agency responses, for meeting preparation, or for taking a position.
prepare-labelling-negotiation-brief
Structures the clinical pharmacology input to a labelling negotiation — assembling the evidence for each CP labelling position, mapping each position to its regulatory precedent, and identifying where the evidence supports the position and where it does not. Use when preparing for a labelling review or negotiation meeting. Do not use for drafting label text, for taking a negotiating position, or for predicting what an agency will accept.
author-applicants-position
Drafts and reviews the clinical pharmacology applicant's-position sections of a regulatory briefing package — each position stated as a claim with its scope, the evidence that supports it, the pre-specified rule it rests on, its limitations, and its residual gaps — structured so that every position is auditable against the cited evidence and no position reads as agreed or accepted. Use this skill when someone asks to draft or review applicant's positions for a regulatory interaction, stress-test positions against their evidence, or check that every position is supported. Example: "Please to draft or review applicant's positions for a regulatory interaction, stress-test positions against their evidence." Do not use for the meeting-request letter itself, for responding to questions an agency already sent, for CTD summary content, for the question-set design, or for any request to assert that a position is agreed or will be accepted.