Skip to content

malekokour/clinpharm-pmx-skills / skills/assess-development-plan-gaps

assess-development-plan-gaps

Verified

Assesses 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.

FileKindSize
PASTE.mdmarkdown22.4 KB
README.mdmarkdown7.8 KB
SKILL.mdskill md22.7 KB
assets/guidance-index.mdmarkdown5.2 KB
references/development-extension-modes.mdmarkdown5.4 KB
references/evidence-hierarchy.mdmarkdown2.7 KB
references/human-review.mdmarkdown2.4 KB
references/output-states.mdmarkdown2.5 KB
references/source-preflight.mdmarkdown2.8 KB
scripts/assess_coverage.pyexecutablescript3.0 KB
scripts/findings.pyscript4.7 KB
scripts/public_development_intelligence.pyexecutablescript15.9 KB
scripts/renal_staging.pyexecutablescript1.7 KB

references/output-states.md

View on GitHub
---
contract: output-states
version: "1.0"
owner: Malek Okour
reviewed: "2026-08-04"
consumers: [review-csr-pk-consistency]
---

# Output states

Three markers exist so that missing evidence is never filled by invention. Use
the exact tokens; they are greppable and they appear in evaluations.

| Marker | Means | Use when |
|---|---|---|
| `NEEDS_INPUT` | The check is possible, but a required input is absent | The user can supply the missing artefact and the check will then run |
| `UNKNOWN` | The evidence is present but does not determine an answer | The documents genuinely do not say, and no amount of re-reading will settle it |
| `CANNOT_ASSESS` | The check cannot be performed at all in this configuration | Extraction failed, the format is unsupported, or the check is out of scope for the selected mode |

## Rules

1. **A marker is a result, not a failure.** Emit it plainly, in the same output
   structure as any other finding, with the same location fields. Do not bury it
   in prose and do not apologise for it.

2. **Every marker names what would resolve it.** `NEEDS_INPUT: Table 14.2.4 not
   supplied — dose-proportionality claim cannot be reconciled` is useful.
   `NEEDS_INPUT` alone is not.

3. **Never substitute a plausible value.** If a number is required and absent,
   the answer is a marker, not an estimate, not a typical value, and not a value
   carried over from a similar document.

4. **Never convert a marker into a conclusion.** "No discrepancy found" and
   "could not check" are different results. Reporting the second as the first is
   the most consequential error this contract prevents.

5. **Coverage is stated numerically.** Any output that reconciles values reports
   how many were checked and how many could not be, so a reader can tell the
   difference between a clean document and an unread one. A completeness claim
   without a denominator is unfalsifiable.

## Mechanical finding versus scientific interpretation

A deterministic check produces a **mechanical finding**: two strings differ, a
unit is inconsistent with the stated convention, a ratio does not recompute.

A mechanical finding is never reported as a scientific conclusion. The output
distinguishes them explicitly:

- *mechanical* — "Synopsis states 412 ng·h/mL; Table 14.2.1 states 481 ng·h/mL.
  Values differ."
- *not permitted* — "The synopsis value is wrong." / "This is a minor issue."
  / "The correct value is 481."

Which value is correct, and whether the difference matters, are scientific
judgements reserved for a qualified human reviewer.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall