# Crisis Boundary Protocol > Activate whenever the task involves preparing peer supporters, volunteers, mentors, or community workers for moments that exceed their scope — crisis escalation procedures, warm handoff design, scope-of-role training, safety protocol development for peer and community programs, or "what do I do when someone is in crisis." Trigger on any program design that puts non-clinical helpers in contact with people who may experience crisis. Fire at PROGRAM DESIGN time — the moment of crisis is the worst possible time to be designing the crisis response, and every peer program will meet that moment eventually. - Skill: `forexgod21/crisis-boundary-protocol` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add forexgod21/crisis-boundary-protocol` - Raw SKILL.md: https://api.skillmd.com/api/skills/forexgod21/crisis-boundary-protocol/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - License: CC BY 4.0 - Author: Forexgod21 (https://skillmd.com/u/forexgod21) - Updated: 2026-09-21 - Page: https://skillmd.com/skills/forexgod21/crisis-boundary-protocol --- # Crisis Boundary Protocol **Attribution:** YourVisionYourCreation LLC — yourvisionyourcreation.com **Doctrine class:** YVYC original — recovery category --- ## Universal So-What Every peer program will eventually hold a moment that exceeds it. The question is never whether that moment comes — it is whether the program designed its response in calm or improvises it in fire. The boundary is not a wall that abandons people; it is a bridge, built in advance, that carries them to the help the moment requires. Knowing exactly where your role ends and how to hand off warmly is not a limitation of peer work. It is peer work, done right. --- ## Core Doctrine ### 1. The Scope Line — Drawn in Calm, In Writing Every peer or community support role documents, before service begins: - What this role IS equipped and authorized to hold - What it is NOT — and for each not, WHERE it goes instead - The scope line is drawn by the organization with clinical consultation, not improvised per person per moment - Every supporter can state the line from memory, because the moment that tests it will not wait for a manual lookup ### 2. Recognition Without Diagnosis Peer supporters are trained to RECOGNIZE that a moment has exceeded scope — never to diagnose what it is: - The trigger list is behavioral and concrete, set by the program's clinical advisors: expressions of intent to harm self or others, safety concerns, medical emergencies, acute states the supporter is not trained for - The standing rule that removes the judgment burden: **when unsure, escalate.** A false alarm costs an awkward conversation; a missed alarm can cost far more. The protocol makes over-caution the cheap, honored default. - Recognition training uses scenarios, practiced BEFORE they are needed — a protocol never rehearsed is a rumor (the same law as every rollback plan) ### 3. The Warm Handoff Standard How the bridge is crossed matters as much as that it exists: - **Stay connected:** the supporter does not vanish at escalation — "I'm going to get someone who can help with this, and I'm staying right here" — presence continues while qualified help engages - **The person is informed:** what is happening and why, in plain words — escalation done TO a person breaks trust; escalation done WITH them keeps it - **Directory pre-verified:** crisis lines (in the US, the 988 Suicide & Crisis Lifeline, with the Veterans Crisis Line option), local crisis teams, emergency services, on-call clinical contacts — numbers verified on a schedule, because a dead number in a crisis binder is a designed failure - **Follow-through:** the handoff is complete when qualified help HAS the person, not when a number has been dialed ### 4. Honesty Doctrine — No Secret-Keeping Promises - The limits of confidentiality are stated at the START of every peer relationship, plainly: safety concerns cannot stay secret, and the supporter will be honest about what they must act on - The forbidden promise: "I won't tell anyone" — a supporter who promises secrecy around safety has promised something the role cannot deliver, and the broken promise lands at the worst moment - The honest version builds MORE trust, not less: "most of what we talk about stays between us — the exception is your safety, because that comes first for me" ### 5. After the Moment — The Supporter's Debrief Escalations mark the supporter too: - Every escalation triggers a debrief with a supervisor or designated support — within a defined window, not "when things calm down" - The debrief separates two questions that must never merge: did the PROTOCOL work (process review), and how is the SUPPORTER (human review) — a process critique delivered to a shaken human teaches supporters to hide escalations - Patterns across debriefs feed protocol revision: the protocol is versioned and improves, like every living document in the doctrine ### 6. Program-Level Duties The boundary is an organizational responsibility, not an individual burden: - Training before contact: no supporter meets people in recovery before scenario-based crisis boundary training - Coverage architecture: someone qualified is always reachable during service hours — a peer program without a clinical backstop is a bridge with no far bank - Documentation of every escalation: what was observed (behavioral, factual), what was done, who took the handoff, when — written the same day - The protocol itself is reviewed with clinical advisors on a cadence and after every activation --- ## Common Failure Modes | Failure | Cause | Correction | |---|---|---| | Supporter freezes at the moment | Protocol existed on paper, never rehearsed | Scenario training before contact, drills on cadence | | Supporter tries to hold what exceeds them | "Referring feels like abandoning" | Warm handoff standard: staying present IS the peer work | | Trust destroyed by an escalation | Escalation done TO the person | Informed, plain-words, WITH the person | | Crisis binder full of dead numbers | Directory never verified | Scheduled verification, owner named | | Secret promised, then broken | Confidentiality limits hidden until tested | Honesty doctrine at relationship start | | Supporters hide near-misses | Debriefs that feel like tribunals | Process review and human review, separated | --- ## Non-Negotiables 1. The scope line is written, clinically informed, and memorized — before contact. 2. When unsure, escalate — over-caution is the honored default. 3. Handoffs are warm: present, informed, followed through. 4. No secret-keeping promises around safety — ever. 5. Every escalation gets a same-day record and a supporter debrief. 6. No peer program operates without a qualified backstop reachable during service hours. --- ## Boundary Note This skill governs program design and role discipline for non-clinical supporters. It is not crisis intervention guidance and does not replace clinical protocols, professional training, or local emergency procedures. Anyone in immediate danger should contact emergency services; in the US, the 988 Suicide & Crisis Lifeline is available by call or text, with a dedicated option for veterans. --- *YourVisionYourCreation LLC — yourvisionyourcreation.com* *Licensed under CC BY 4.0*