malekokour/clinpharm-pmx-skills / skills/build-work-context
build-work-context
VerifiedBuilds, updates, refreshes, and exports portable work context for pharmaceutical and biotech professionals. Use this skill whenever someone wants AI to understand their pharma role, department, responsibilities, projects, sources, terminology, constraints, approval rules, or preferred deliverables; asks to be interviewed; mentions a work profile, professional constitution, project instructions, reusable context, Copilot or ChatGPT context, or wants to combine an existing context file with new project documents. Produces a professional context, project capsule, working pack, and change summary without inventing facts. Do not use for patient-specific clinical decisions or as a substitute for qualified scientific, regulatory, or medical judgment.
| File | Kind | Size |
|---|---|---|
| PASTE.md | markdown | 8.2 KB |
| README.md | markdown | 936 B |
| SKILL.md | skill md | 8.4 KB |
| assets/AI-Working-Pack.template.md | markdown | 774 B |
| assets/Context-Change-Summary.template.md | markdown | 494 B |
| assets/My-Pharma-Work-Context.template.md | markdown | 1.7 KB |
| assets/Project-Context.template.md | markdown | 808 B |
| references/context-contract.md | markdown | 3.8 KB |
| references/department-prompts.md | markdown | 3.3 KB |
| references/evidence-hierarchy.md | markdown | 2.7 KB |
| references/human-review.md | markdown | 2.4 KB |
| references/interview-and-modes.md | markdown | 3.8 KB |
| references/output-states.md | markdown | 2.5 KB |
| references/safety-and-evidence.md | markdown | 3.0 KB |
| references/source-preflight.md | markdown | 2.8 KB |
| scripts/context_validation.pyexecutable | script | 6.4 KB |
| scripts/findings.py | script | 4.7 KB |
| scripts/validate_context.pyexecutable | script | 1.7 KB |
references/department-prompts.md
View on GitHub# Department-specific interview prompts
Read only the selected function. These are optional probes, not facts about the
user or universal descriptions of each department.
## Clinical pharmacology and pharmacometrics
- Which decisions do you support: development strategy, dose selection,
labeling, study design, analysis review, or regulatory response?
- Which analysis artifacts govern your work?
- What constitutes reproducible evidence in your environment?
- Which conclusions require pharmacometrician, clinician, statistician, or
regulatory sign-off?
- How should model assumptions, uncertainty, and source traceability appear in
deliverables?
## Biostatistics and data science
- Which study phases, endpoints, and analysis types are in scope?
- What are the governing protocol, SAP, data standards, and programming
conventions?
- Which outputs require independent programming or statistical review?
- How should estimands, populations, missing data, and multiplicity be handled
in summaries?
- Which tools and validated environments are permitted?
## Clinical development and operations
- Which studies, countries, vendors, and milestones are in scope?
- What is the authority order among protocol, plans, systems, trackers, and
meeting decisions?
- Which operational changes require study-team, quality, medical, or regulatory
approval?
- Which risks, dependencies, and actions should be surfaced first?
- Which systems remain operational truth rather than the generated context?
## Regulatory affairs
- Which jurisdictions, submission types, and product stages are in scope?
- Which approved documents and agency interactions govern the response?
- How should commitments, questions, comments, and response ownership be
tracked?
- Which statements require legal, medical, statistical, or functional review?
- What must remain draft or prepare-only?
## Medical affairs
- Which audience and scientific-exchange boundary applies?
- Which approved evidence and reference set governs?
- What distinguishes scientific response, medical education, field insight, and
promotional use?
- Which outputs require medical, legal, regulatory, or compliance review?
- How should balanced evidence, limitations, and citations appear?
## Pharmacovigilance and safety
- Which case, signal, aggregate-report, or governance workflow is in scope?
- Which controlled terminology and safety systems govern?
- What are the escalation, seriousness, expectedness, and timing boundaries?
- Which judgments require a safety physician or qualified reviewer?
- What information is prohibited from the current environment?
## CMC, quality, and manufacturing
- Which product, process, site, lifecycle stage, and quality system are in scope?
- Which specifications, methods, records, procedures, and change controls govern?
- Which activities occur in a validated environment?
- Which deviations, risks, or decisions require quality-unit approval?
- How should traceability, version, and effective-date information appear?
## Market access, commercial, and strategy
- Which market, audience, product stage, and decision are in scope?
- Which claims, assumptions, forecasts, and evidence sources govern?
- What separates strategic exploration from approved external messaging?
- Which outputs require medical, legal, regulatory, privacy, or brand review?
- What level of uncertainty and scenario framing is required?
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |