skills/legal/advance-directive-vs-polst/SKILL.md
Produces a plain-language comparison of advance directives and POLST/MOLST forms, covering legal status, clinician signatures, emergency precedence, clinical appropriateness, and document coordination. Use when the user asks about advance directive vs. POLST, living will vs. DNR, which document EMS follows, POLST vs. MOLST vs. POST, whether a healthy person needs a POLST, or document coordination in elder law, estate planning, or serious illness contexts.
npx skillsauth add casemark/skills advance-directive-vs-polstInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Compares advance directives (legal planning documents) with POLST/MOLST forms (clinician-signed medical orders). These occupy different legal and clinical lanes — confusing them creates dangerous gaps in emergency care.
Gather before drafting (skip if user says "use defaults"):
Defaults if no response: general comparison, no state-specific claims, healthy adult context, educational memo format.
| Feature | Advance Directive | POLST / MOLST | |---|---|---| | Nature | Legal planning document | Clinician-signed medical order | | Purpose | Appoints agent; expresses values | Translates preferences into actionable orders | | Who signs | Principal (+ witnesses/notary per state) | Clinician + patient or rep | | Who it instructs | Agents, families, downstream clinicians | EMS, hospitals, facilities — immediately actionable | | Scope | Broad: values, agent authority, end-of-life wishes | Specific: CPR, hospitalization, ventilation, nutrition | | Appropriate for | All competent adults | Serious illness, advanced frailty, limited life expectancy | | EMS usability | Generally not actionable at scene | Yes — designed for field portability | | Clinician signature? | No | Yes — invalid without it |
POLST takes practical precedence in the field. EMS looks for medical orders, not legal documents.
Never promise "EMS will always follow" any form. Availability, local protocol, validity, and state registry participation determine what gets followed.
POLST is not for healthy adults. Use the "Surprise Question": Would you be surprised if this patient died in the next year? If yes → POLST is premature.
Nursing home warning: Facilities sometimes present POLST as routine intake paperwork. Clients should not sign without a goals-of-care discussion with their physician about actual prognosis.
Advance directive = values framework + agent authority. POLST = current clinical goals as orders. They must be consistent.
Draft a memo or client handout covering:
Use analogy: advance directive = "constitution," POLST = "executive order."
Ask after delivering:
Adapt to the state's label before finalizing:
| Acronym | States | |---|---| | POLST | CA, OR, WA, others | | MOLST | NY, MD | | MOST | NC, SC | | POST | ID, TN, UT, WV, others | | TPOPP | MN | | Out-of-Hospital DNR only | FL, TX (limited scope) |
Verify via the National POLST program directory before asserting any state's form name.
Scope: This skill explains and compares — does not draft documents, determine capacity, or resolve validity disputes.
Anti-hallucination:
[VERIFY]Quality checklist:
[VERIFY]Required disclaimer: This is general legal information, not legal advice. Review with a licensed attorney before use in any client matter and with a licensed clinician before any medical decisions are implemented.
development
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
tools
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
development
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
testing
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.