Healthcare Project Context

When To Use

Invoke to bootstrap reusable project context for a healthcare repository. Use once per project, or when jurisdiction, audience, or project stage are unclear, so downstream healthcare skills (health-compliance-review, health-docs, health-product-discovery, health-refactor) don’t need to re-derive the same answers independently.

Overview

Healthcare skills repeatedly need the same project-level answers before they can give good guidance:

• Which regulatory market applies: US, EU, both, or unclear?
• Who does the product primarily serve: provider, patient, payer, administrative, mixed, or unknown?
• Is the target repository an existing system or a greenfield effort?

This skill answers those questions from repository evidence first, then persists the result in .health-context.yaml at the target repository root so future healthcare skills can reuse it instead of re-deriving it every time.

Do not force a confident classification from repo-shape alone. Sparse repos, scaffolds, and agent-tooling-only directories such as .agents/, .claude/, .codex/, or .gemini/ are weak evidence and usually mean one or more fields should remain unclear.

Workflow