From pm-research
Write clear, plain English patient communications for any healthcare context. Use when asked to write a patient letter, patient information leaflet, appointment letter, test results letter, discharge summary for patients, or health education content. Targets accessible reading level with clear next steps.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-research:patient-communicationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Writes patient-facing healthcare communications in plain, accessible language — targeting UK Grade 6 / US Grade 8 reading level.
Writes patient-facing healthcare communications in plain, accessible language — targeting UK Grade 6 / US Grade 8 reading level.
WARNING: All patient communications must be reviewed and approved by a qualified healthcare professional before sending. This skill produces drafts only.
[Date]
Dear [Patient name],
Re: [Clear subject line in bold]
[Opening paragraph: State clearly what this letter is about. No preamble.]
[Main content — short paragraphs, 2-3 sentences each. Bullet points for instructions. Bold anything the patient must do or remember.]
What happens next:
If you have questions: Contact us at [phone] between [hours] or email [address].
If you feel unwell before your appointment, please [specific instruction].
Yours sincerely, [Name, Title, Department]
[Plain language title]
What is [topic]? [2-3 plain English sentences. Explain technical terms immediately.]
Why has this been recommended for me? [Personalised clinical reason in patient terms]
What will happen? [Numbered step by step]
What are the benefits? [Honest statement]
What are the risks? [Common first, then rare but serious. Use frequencies: "About 1 in 10 people..." not "10% incidence"]
What should I do to prepare? [Specific instructions]
When should I contact someone? [Specific signs — not vague. "Temperature above 38C" not "if you feel unwell"]
Your [test name] results — [Normal / Abnormal] — stated in the FIRST sentence, never paragraph 3.
[What this means in plain English]
What happens next: [Clear next steps. If no action, say so explicitly.]
npx claudepluginhub mileadev/pm-claude-skills --plugin pm-researchGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
2plugins reuse this skill
First indexed Jul 8, 2026