awell-health

Build or extend an Awell extension in this monorepo from a vendor's API docs and a user's intent (e.g. "add an action that sends an SMS via Vendor X", "add a webhook for booking.created"). Use whenever the task is to create a new extension under extensions/ or add an action/webhook/setting to an existing one. Covers the full loop: plan → scaffold → implement (settings, actions, webhooks, error mapping) → test → run/verify with the CLI → PR. Do NOT use for unrelated repo work (src/lib/, the extensions-core framework, CI config, or root dependency changes without an extension need).

Branch naming, commit messages, PR titles, PR body structure, labels, and the pre-PR checklist for the awell-extensions repo. Use whenever you are about to create a branch, write a commit, or open/title a PR here — for ANY change, not just extensions. Do NOT use for version bumps (CI auto-bumps on merge), release PRs (release/* is owned by the release workflow), or automated dependency PRs.

Run, test, and verify an EXISTING Awell extension in this monorepo — execute an action or replay a webhook against the real handler, run its Jest tests, and interpret failures. Use whenever the task is "test / run / try / verify / debug extension X" or "does action Y work". For BUILDING or editing an extension, use the building-awell-extensions skill instead.

Tag a new Spire release with structured release notes. Use when the user says "/release", "tag a release", "cut a release", or "release notes". Determines version bump (major/minor/patch) from commit types since last tag.

Brainstorm and capture design thinking in a design bead. Use when the user wants to explore an idea, brainstorm an approach, or design a system before committing to work items. Triggers on "/spire-design", "let's brainstorm", "let's design", or when the user is exploring ideas that should be captured.

Resolve Dolt merge conflicts in Spire towers using direct `dolt sql` sessions instead of `spire board`, store APIs, or other schema-initializing paths. Use when `spire pull` or `spire sync --merge` leaves unresolved conflicts, when Dolt reports `dolt_conflicts` or `dolt_constraint_violations`, or when the user explicitly asks for `/spire-conflicts`.

Read and update Hill Chart data (hills, scopes, and roadmap goals) over its REST API. Use when the user wants to look up a hill by name, pull scopes or roadmap goals for context, or create/update/delete scopes and goals in the Hill Chart app.

Write, debug, and explain BigQuery SQL against Awell's exported care-flow data model. Use when the user wants to query, analyze, or extract data or insights from Awell's BigQuery datasets (care flows, activities, data points, patients, forms, tracks, steps, timers, graph nodes/edges), turn a natural-language question into SQL, choose the right table or columns, or fix an existing Awell BigQuery query. Covers the project/customer dataset layout, realtime views, and the current patient_data tables that supersede the deprecated patient_profiles table.