mcpField
D
digital-health-ux-planning

digital-health-ux-planning

github.com/stanfordspeziDesign & UI26128 installsUpdated 5w ago
Repository

About digital-health-ux-planning

A UX planning skill for digital health teams designing patient, clinician, and participant experiences. It structures journeys around user needs, trust, accessibility, and clinical safety rather than assumed screens or platforms.

Key features

  1. 01User segment analysis
  2. 02End-to-end journey mapping
  3. 03Onboarding and recurring workflow planning
  4. 04Engagement and accessibility review
  5. 05UX brief with risks and open questions

Use cases

  1. 01Planning patient enrollment and consent-adjacent flows
  2. 02Designing recurring health tracking tasks
  3. 03Reviewing engagement for burden and ethics

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/stanfordspezi/spezivibe --skill digital-health-ux-planning

After installing, type/digital-health-ux-planningin Claude Code to confirm it loaded.

Details

From the project README

UX Planner

Plan user experience flows for digital health products without assuming a specific client technology.

When to Use

Use this skill when you need to:

  • design end-to-end journeys for patients, participants, clinicians, or coordinators
  • plan onboarding and consent-adjacent flows
  • structure recurring health tracking or task completion workflows
  • think through engagement, motivation, and accessibility

Working Style

Begin with the people, decisions, and moments that matter. Do not start with screens.

Clarify:

  1. primary users
  2. core jobs to be done
  3. highest-friction moments
  4. what users need to understand, decide, or complete
  5. what success looks like for both the user and the program

Planning Framework

1. User Segments

Identify:

  • primary users
  • secondary users
  • staff or caregiver roles
  • user constraints such as health literacy, accessibility needs, fatigue, or limited time
2. Core Journeys

Map the main flows in plain language, for example:

  • discover and enroll
  • learn what the product is for
  • provide consent or required acknowledgements
  • complete the first meaningful task
  • return for ongoing use
  • review progress or history
  • get help or recover from confusion
3. Onboarding

Plan what users need at the beginning:

  • orientation and trust-building
  • account setup if applicable
  • permissions or access requests only when needed
  • profile or baseline setup
  • first action that creates value quickly

Challenge any onboarding flow that asks for too much too soon.

4. Day-to-Day Workflow

Describe the recurring experience:

  • what prompts the user to return
  • what they see first
  • what they are expected to do
  • how completion and progress are communicated
  • what happens when they skip, fall behind, or lose context
5. Engagement Strategy

Consider:

  • reminders
  • summaries
  • milestone feedback
  • streaks or encouragement, if appropriate
  • how to avoid manipulation, shame, or alert fatigue
6. Accessibility and Inclusion

Review:

  • readability and plain language
  • color contrast and visual hierarchy
  • support for assistive technologies
  • cognitive load
  • language, cultural, and trust considerations

Deliverable Format

Produce a concise UX planning brief with:

  • primary user segments
  • top user journeys
  • onboarding strategy
  • recurring workflow design
  • engagement principles
  • accessibility and inclusion notes
  • unresolved risks or UX questions

Save the brief as docs/planning/ux-brief.md in the project repository.

Guardrails

  • Do not assume mobile tabs, specific screens, or platform conventions unless implementation context requires it.
  • Prefer user goals and decision points over UI inventories.
  • Keep trust, burden, and accessibility central.
  • Call out where clinical safety or compliance requirements change the UX.

Checklist

  • User segments identified
  • Core journeys mapped
  • Onboarding scoped to the minimum necessary steps
  • Day-to-day workflow defined
  • Engagement strategy reviewed for burden and ethics
  • Accessibility and inclusion considerations captured
  • Major UX risks and open questions documented

Comments

Markdown supported