malekokour/clinpharm-pmx-skills / skills/assess-development-plan-gaps
assess-development-plan-gaps
VerifiedAssesses 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.
| File | Kind | Size |
|---|---|---|
| PASTE.md | markdown | 22.4 KB |
| README.md | markdown | 7.8 KB |
| SKILL.md | skill md | 22.7 KB |
| assets/guidance-index.md | markdown | 5.2 KB |
| references/development-extension-modes.md | markdown | 5.4 KB |
| references/evidence-hierarchy.md | markdown | 2.7 KB |
| references/human-review.md | markdown | 2.4 KB |
| references/output-states.md | markdown | 2.5 KB |
| references/source-preflight.md | markdown | 2.8 KB |
| scripts/assess_coverage.pyexecutable | script | 3.0 KB |
| scripts/findings.py | script | 4.7 KB |
| scripts/public_development_intelligence.pyexecutable | script | 15.9 KB |
| scripts/renal_staging.pyexecutable | script | 1.7 KB |
references/evidence-hierarchy.md
View on GitHub---
contract: evidence-hierarchy
version: "1.0"
owner: Malek Okour
reviewed: "2026-08-04"
consumers: [review-csr-pk-consistency]
---
# Evidence hierarchy and source locators
## Precedence
When two supplied documents disagree, precedence decides which is treated as the
expected value — it never decides which is scientifically correct.
1. The **locked source output** the value derives from (analysis outputs,
parameter datasets, statistical outputs).
2. The **pre-specified rule document** (analysis plan, protocol and its
amendments) for conventions: units, rounding, exclusions, estimation method.
3. The **document under review**, which is the object being checked, not an
authority about itself.
4. Any **summary or derived document**, which is never authoritative over the
source it summarises.
A user may declare a different order for a specific task. Record the declared
order in the output; do not apply it silently.
## Locators are mandatory
Every finding carries enough location for a reviewer to open the document and
land on the exact statement without searching:
- document identity and version;
- section number and heading, or table/figure number;
- row and column where the value sits in a table;
- page number when the format provides one.
A finding without a locator is not reportable. It is indistinguishable from an
assertion, and it costs a reviewer more time to verify than to redo.
## Exact values are preserved verbatim
Numbers, units, qualifiers, negations, populations, time points and statistical
descriptors are reproduced **exactly as written**, including the original
precision and any trailing zeros.
Do not normalise, round, convert, or tidy a value on the way into a finding. A
rounding difference may itself be the defect, and a silent conversion destroys
the evidence that would show it.
Where a comparison requires a tolerance — because the two documents legitimately
use different precision — apply the tolerance rule from the analysis plan and
report the rule that was applied alongside the finding.
## Contradictions are preserved, not resolved
When sources conflict, the output records **both statements with both
locators**, and marks the item as a contradiction for human resolution.
Never silently harmonise two sources. Never pick the one that looks more
plausible. Never average them. Never report only the one that matches the
document under review.
The contradiction is the finding. Resolving it is the reviewer's job.
## Staleness
A value inherited from a superseded document version is a distinct finding
class from a numeric mismatch, and is reported as such: the current document, the
version it appears to reflect, and the version that is authoritative.
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: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |