Veteran playbook for the human conversations in hospice referral work — the hospice-vs-palliative distinction, the timing problem, the myth-and-objection responses ('giving up', 'too soon', 'my doctor didn't mention it', 'I want to keep fighting'), and a values-first, no-false-promise framing approach. Consulted by goals-of-care-conversation-coach. Empathy and accuracy; never a scripted guarantee or a pressure tactic.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hospice-referral-sales:goals-of-care-conversationsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** help `goals-of-care-conversation-coach` prepare for the hardest, most human part of the job — supporting an honest conversation in which hospice is offered as access to support, never sold, never pressured.
Purpose: help goals-of-care-conversation-coach prepare for the hardest, most human part of the job — supporting an honest conversation in which hospice is offered as access to support, never sold, never pressured.
Coach framing, not promises. Never a guarantee of outcome, coverage, or eligibility; never a pressure tactic; never the liaison substituting for the patient's clinician. The conversation is values-first — the patient's goals lead. (../CLAUDE.md §3 #3, #10.)
| Palliative care | Hospice | |
|---|---|---|
| Prognosis | Any stage of serious illness | Terminal, ~6 months or less |
| Curative treatment | Continues alongside | Forgone for the terminal illness (revocable) |
| Setting | Any | Home, facility, inpatient unit |
| Payment | Usual insurance | Medicare Hospice Benefit (and most payers) |
Conflating the two is a leading cause of late referrals. When a patient is not yet hospice-appropriate, palliative care is often the honest next step — and offering it builds the trust that brings the hospice referral later.
The core failure in hospice is the too-late referral — a length of stay measured in days, denying the family the benefit. The windows when the conversation is both possible and kind: a hospitalization, a clear functional decline, a "would you be surprised if this patient died in the next year?" moment. Earlier is kinder.
| They say | Empathy-first reframe (never pressure) |
|---|---|
| "Hospice is giving up." | "It's not giving up — it's choosing how to live this time, with the most support possible. The focus shifts to comfort and to what matters most to [patient]." |
| "It's too soon." | "Many families tell us afterward they wish they'd started sooner. And hospice isn't a one-way door — if things improve or you want to resume treatment, you can revoke and do that." |
| "My doctor didn't mention it." | "Let's bring your doctor into this — I can support the conversation. Sometimes it just hasn't come up yet, not that it isn't appropriate." (Then the clinician-framing path.) |
| "I want to keep fighting." | "That makes complete sense. There's a difference between fighting the disease and fighting for the best quality of life in the time ahead — hospice is the second kind of fight, with a whole team behind you." |
Each is said once, with empathy, and never pushed. Listen more than you reframe.
Help a referring physician introduce hospice as continuity, not abandonment: "hoping for the best while preparing for what's ahead," hospice as an addition of support (a team, 24/7 availability, symptom management, family support, bereavement), not a withdrawal of care. The clinician leads the medical conversation; the liaison supports.
The patient's stated goals, the family's specific fears, the unspoken question ("are we doing the wrong thing?"), and the moment to slow down rather than push. A conversation that ends with the family feeling heard — even without a same-day election — is a success; pressure that produces a reluctant yes is not.
hospice-eligibility-criteria skill / hospice-eligibility-educator.hospice-sales-compliance skill / hospice-sales-compliance-advisor.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.