Veteran playbook for hospice key-referral-partner work — the partner business-review structure (patient outcomes, access improvements, honest assessment, shared goals, joint plan), the account-plan template (relationship map, whitespace by unit/service line, growth plays, risks), the relationship-recovery sequence, and the partner-health read. Consulted by referral-account-manager. Patient-outcome-led; never retain or grow a partner with an un-cleared value exchange.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hospice-referral-sales:referral-account-planningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** help `referral-account-manager` run reviews and build plans that retain and grow referral partners by leading with **patient and family outcomes**. The agency's referral count is never the headline.
Purpose: help referral-account-manager run reviews and build plans that retain and grow referral partners by leading with patient and family outcomes. The agency's referral count is never the headline.
Five parts, in this order:
Cadence: quarterly for key partners; align to the partner's rhythm. Bring program-level data, never patient-identifying data.
The templates/referral-account-plan.md is the fillable version.
Growing referrals from an existing partner beats opening a cold one on every measure. Natural next steps: other units, other physicians in the group, other service lines, and earlier referrals (the biggest whitespace of all — moving a partner's average referral from "last days" to "months" serves more patients and grows volume simultaneously).
A poor admission experience — a slow after-hours admit, a communication breakdown, a family complaint — handled visibly and fast rebuilds referrals better than a quiet good quarter. The sequence: acknowledge fast → contain/fix → root-cause honestly → prove the fix with data → re-earn the next referral. Run the declined-referral root-cause tree to separate a service cause from an eligibility or competitor cause.
Defend before a competitor is entrenched. Reinforce delivered outcomes (bring the review data), widen relationships, and close the specific gap the competitor exploits (responsiveness, after-hours admits, a service line) — within compliance limits. You never defend a partner by offering something of value that crosses the anti-kickback line; loyalty is earned with outcomes, never bought.
Green/Yellow/Red on: referral-volume trend, conversion quality (are their referrals eligible and timely?), service incidents, relationship coverage (single vs multi-thread), engagement (review attendance, responsiveness), and competitor activity. A Red on any one is a retention action, not a footnote.
admissions-funnel-analytics skill / admissions-conversion-coach.referral-territory-development skill / referral-development-strategist.hospice-sales-compliance skill / hospice-sales-compliance-advisor (mandatory).hospice-eligibility-criteria skill / hospice-eligibility-educator.npx claudepluginhub mcorbett51090/ravenclaude --plugin hospice-referral-salesGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.