Borrowing it
Nothing to install: this file belongs to charliehzm/medharness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/charliehzm/medharness/main/.claude/skills/prd-implementation-precheck/SKILL.mdgit clone --depth 1 https://github.com/charliehzm/medharnessWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/charliehzm/medharness/prd-implementation-precheck)<a href="https://agentmods.dev/skills/charliehzm/medharness/prd-implementation-precheck"><img src="https://agentmods.dev/badge/skills/charliehzm/medharness/prd-implementation-precheck/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/charliehzm/medharness/prd-implementation-precheck"><img src="https://agentmods.dev/badge/skills/charliehzm/medharness/prd-implementation-precheck.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00192 | $0.00904 |
| Opus 5 | $0.00096 | $0.00452 |
| Sonnet 5 | $0.00038 | $0.00181 |
| Haiku 4.5 | $0.00019 | $0.00090 |
Grade A, and why
prd-implementation-precheck scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Implementation Precheck
The Step 1 / Step 2 gate. Catches PRD / TDD ambiguity before OpenSpec is generated, so we don't have to retrofit later.
Core mental model
A PRD is implementation-ready when:
- Every feature has a defined boundary (in/out of scope, both stated)
- Every acceptance criterion has a measurable test hook
- Every cross-team dependency has a named owner
- Every metric has a baseline + target + measurement method
- The scope is broken into shippable stages, each with its own DoD
This skill scans for violations and emits a gap report.
What this skill produces
PRD_PRECHECK_REPORT.md with:
- Blockers (must fix before proceeding)
- Warnings (should fix; can proceed with explicit override)
- Suggestions (informational)
When NOT to use
- Writing or expanding a PRD (use
prd) - Compliance pre-check (use
compliance-precheckStep 0) - Architecture review (use Plan agent / openspec-new-change)
Active context bundle
Always load first
- This
SKILL.md - The target PRD / TDD file
reference/precheck-checklist.md— 30+ canonical gapsreference/severity-rubric.md
Workflow
- Read PRD / TDD top to bottom.
- Run checklist — for each item, mark present / missing / vague.
- Stage breakdown audit — does the PRD propose a stage 1 / 2 / 3 split? Each stage has its own DoD?
- Metric audit — every KPI has baseline + target + measurement method?
- Dependency audit — every "needs X from team Y" has an owner + due date?
- Compose report — group by severity, point at exact PRD section/line.
- Hand off — if blockers > 0, send back to
prdSkill; if only warnings, surface to user for explicit accept/fix decision.
Hard gate / soft gate
Hard for blockers. Warnings can be accepted with sign-off (recorded in report).
Common failure modes
- "Looks complete" trap — PRD reads fluently but lacks measurable criteria. Mitigation: always demand metric formula, not metric name.
- Stage breakdown handwaved — "Stage 1 MVP, Stage 2 polish" with no scope cut. Mitigation: require feature-level allocation per stage.
- Owner = team name — "Backend team" is not an owner. Mitigation: require named individual + role.
- Acceptance via dogfooding — "users say it's good" is not measurable. Mitigation: require quantitative + qualitative pair.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 82 lines · 192 tokens per session scan A 8669b2a98528
prd-implementation-precheck is a skill published in the GitHub repository charliehzm/medharness (86 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 192 tokens to every session and 904 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
hipaa-review
Performs a HIPAA Security Rule compliance review against all Administrative, Physical, and Technical Safeguards defined in 45 CFR Part 164, Subpart C. Auto-invoked when discussing healthcare data security, ePHI protection, HIPAA audit readiness, or business associate compliance. Evaluates required and addressable…
HIPAA Compliance Testing
Testing HIPAA compliance for healthcare applications including PHI handling, audit logging, access controls, and data encryption verification.
Healthcare Compliance
HIPAA compliance, healthcare regulations, privacy and security standards for medical organizations and providers.
compliance
Use when scoping which regulatory frameworks bind a business — SOC 2, ISO 27001, HIPAA, PCI DSS, EU AI Act, DORA, NIS2 — building a control register with owners and evidence, or standing up the cadence that keeps it audit-ready. NOT drafting privacy-policy/ROPA/DPA or ToS text (that is gdpr-privacy, terms-conditions)…
healthcare-expert
Expert-level healthcare systems, medical informatics, HIPAA compliance, and health data standards. Use when the user mentions medical, HIPAA, HL7, FHIR, or EHR, or when the task involves Healthcare IT, Standards and Protocols, Regulatory Compliance, or Security and Compliance.
performing-soc2-type2-audit-preparation
Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security…