executing-plans
executing-plans
Use 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
openevidence-core-workflow-bAudit an OpenEvidence answer’s EvidenceGrade, citations, and applicability before it informs clinical work. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence core workflow b", "OpenEvidence citations", or a matching workflow request.
Independent GitHub snapshot · Automated classification · Original documentation governs
name: openevidence-core-workflow-b description: >- Audit an OpenEvidence answer’s EvidenceGrade, citations, and applicability before it informs clinical work. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence core workflow b", "OpenEvidence citations", or a matching workflow request. argument-hint: "[response-or-notes-path] [review-question]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.14.0 author: Jeremy Longshore jeremy@intentsolutions.io license: MIT tags:
Treat the displayed grade as a navigation aid, then perform a source-level review of every material claim. Keep inputs minimal, separate observed facts from assumptions, and leave consequential decisions with the named accountable owner.
Use Read, Glob, and Grep to inspect supplied policies, plans, and evidence. Use WebFetch only for current first-party OpenEvidence documentation. Use Write or Edit only when the user requests a named deliverable with an approved destination. Never expose credentials, PHI, recordings, or unrestricted environment output.
Use only the official OpenEvidence web/mobile sign-in or an institution-approved access path. Do not invent API keys, OAuth clients, SDK credentials, service accounts, or private endpoints. Never ask a user to reveal a password, session token, cookie, or recovery code.
Do not create or share accounts; change access, roles, agreements, consent, retention, or security settings; enter PHI; record a conversation; copy content into another system; contact a patient; make a diagnosis or treatment decision; submit billing; transmit a support packet; run a production pilot; or represent vendor capabilities without explicit approval from the accountable owner. A qualified professional remains responsible for clinical decisions.
Return scope, current first-party evidence and date, data classification, workflow or findings, citations reviewed, assumptions rejected, clinical and governance owners, approval state, unresolved risk, and the exact next action. Redact patient and credential data.
| Condition | Response |
|---|---|
| Citation unavailable | Mark the linked claim unverified; do not rely on a summary alone. |
| Grade missing | Continue source-level review and state that no grade was available. |
| Source is indirect | Describe the inference and require clinical judgment. |
This compact example shows the minimum reviewable handoff; adapt fields to the approved workflow without adding sensitive data.
Input:
response=de-identified excerpt; decision=screening interval; review=all material claims
Expected handoff:
claims=6; supported=4; uncertain=2; grade=recorded; clinician-signoff=required