Initial commit
This commit is contained in:
34
commands/design-clinical-campaign.md
Normal file
34
commands/design-clinical-campaign.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
name: design-clinical-campaign
|
||||
description: Produces clinical-grade campaign brief with targeting, creative guidance, and review plan.
|
||||
usage: /healthcare-marketing:design-clinical-campaign --product "Cardio AI" --audience providers --channels email,webinar,field --evidence dossier.pdf
|
||||
---
|
||||
|
||||
# Command: design-clinical-campaign
|
||||
|
||||
## Inputs
|
||||
- **product** – product/treatment/service being promoted.
|
||||
- **audience** – providers | payers | patients | mixed.
|
||||
- **channels** – comma-separated (email, webinar, paid_social, display, field, events, referral).
|
||||
- **evidence** – optional link/file with clinical studies, claims, or testimonials.
|
||||
- **objectives** – KPIs (leads, enrollments, prescriptions, education, adherence).
|
||||
|
||||
## Workflow
|
||||
1. **Evidence Review** – summarize key claims, safety considerations, and regulatory constraints.
|
||||
2. **Audience Targeting** – define personas, segments, and channel mix per audience.
|
||||
3. **Messaging Architecture** – craft value pillars, proof points, disclaimers, and CTAs.
|
||||
4. **Creative & Content Plan** – outline asset list, KOL content, and required approvals.
|
||||
5. **Launch & Measurement Plan** – specify KPIs, dashboards, and post-launch reporting cadence.
|
||||
|
||||
## Outputs
|
||||
- Clinical campaign brief (messaging framework, creative requirements, timeline).
|
||||
- Compliance checklist with assigned reviewers and deadlines.
|
||||
- Measurement plan document with KPI definitions + reporting cadence.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `clinical-campaign-strategist` – leads narrative and targeting decisions.
|
||||
- `compliance-marketing-director` – injects regulatory guidance + review path.
|
||||
- `clinical-proof-library` skill – sources evidence and proof points.
|
||||
- `patient-journey-mapping` skill – aligns messaging to journey stages.
|
||||
|
||||
---
|
||||
34
commands/orchestrate-patient-journey.md
Normal file
34
commands/orchestrate-patient-journey.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
name: orchestrate-patient-journey
|
||||
description: Builds compliant patient engagement journey with educational content, consent flows, and support scripts.
|
||||
usage: /healthcare-marketing:orchestrate-patient-journey --condition "Cardio" --stage onboarding --channels email,sms,community --duration 90d
|
||||
---
|
||||
|
||||
# Command: orchestrate-patient-journey
|
||||
|
||||
## Inputs
|
||||
- **condition** – therapeutic area or program name.
|
||||
- **stage** – awareness | consideration | onboarding | adherence | advocacy.
|
||||
- **channels** – email, sms, push, community, field, telehealth (comma-separated).
|
||||
- **duration** – 30d | 60d | 90d | custom timeline for the journey.
|
||||
- **consent-model** – opt-in workflow reference or data policy doc.
|
||||
|
||||
## Workflow
|
||||
1. **Journey Discovery** – gather patient needs, clinical guidance, and support resources.
|
||||
2. **Content & Touchpoint Plan** – outline education modules, reminders, escalation cues per stage.
|
||||
3. **Compliance Layer** – embed consent checkpoints, disclaimers, and escalation procedures.
|
||||
4. **Enablement Pack** – produce scripts, FAQs, and training notes for CS/field teams.
|
||||
5. **Measurement Plan** – define KPIs (engagement, adherence, NPS) and reporting cadence.
|
||||
|
||||
## Outputs
|
||||
- Journey storyboard with touchpoints, messaging, and consent notes.
|
||||
- Enablement kit (scripts, knowledge base outline, escalation tree).
|
||||
- Dashboard/analytics spec for monitoring patient engagement + safety signals.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `patient-engagement-program-manager` – leads journey design + enablement.
|
||||
- `compliance-marketing-director` – validates consent + regulatory requirements.
|
||||
- `patient-journey-mapping` skill – enforces structure + documentation.
|
||||
- `regulatory-review-checklist` skill – ensures approvals before launch.
|
||||
|
||||
---
|
||||
34
commands/run-compliance-review.md
Normal file
34
commands/run-compliance-review.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
name: run-compliance-review
|
||||
description: Executes HIPAA/FDA/FTC compliance review for healthcare marketing campaigns.
|
||||
usage: /healthcare-marketing:run-compliance-review --campaign "Cardio Webinar" --channels email,landing --risk-level moderate
|
||||
---
|
||||
|
||||
# Command: run-compliance-review
|
||||
|
||||
## Inputs
|
||||
- **campaign** – campaign/program identifier or brief ID.
|
||||
- **channels** – comma-separated list (email, landing, paid, webinar, field, events).
|
||||
- **risk-level** – low | moderate | high; influences approval path and SLA.
|
||||
- **claims** – optional file/URL to clinical claims or messaging hierarchy.
|
||||
- **audience** – providers | payers | patients | mixed.
|
||||
|
||||
## Workflow
|
||||
1. **Brief Intake** – pull campaign context, creative, data flows, and offer details.
|
||||
2. **Regulatory Checklist** – evaluate HIPAA, FDA, FTC, regional privacy rules per channel.
|
||||
3. **Gap Analysis** – flag unsupported claims, consent gaps, or escalation requirements.
|
||||
4. **Approval Routing** – generate reviewer list (legal, medical, privacy) with tasks + due dates.
|
||||
5. **Documentation** – log decisions, conditions, and expiration dates in compliance archive.
|
||||
|
||||
## Outputs
|
||||
- Compliance memo summarizing risks, mitigations, and approvals needed.
|
||||
- Reviewer task list with due dates and supporting materials.
|
||||
- Audit-ready packet (evidence, annotated assets, approval history).
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `compliance-marketing-director` – leads assessment + escalation.
|
||||
- `clinical-campaign-strategist` – validates claims vs supporting evidence.
|
||||
- `compliance-briefing-kit` skill – enforces checklist + output format.
|
||||
- `regulatory-review-checklist` skill – ensures routing rules and documentation completeness.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user