@elitedcs/ghl-mcp 3.53.2 → 3.55.0

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@elitedcs/ghl-mcp",
-  "version": "3.53.2",
+  "version": "3.55.0",
   "mcpName": "io.github.drjerryrelth/ghl-command",
-  "description": "GoHighLevel MCP Server for Claude. 232 tools \u2014 full CRM, automation, marketing control, account-wide workflow audit, live funnel-capture verification, and the only programmatic GHL workflow builder, now multi-tenant across client accounts.",
+  "description": "GoHighLevel MCP Server for Claude. 235 tools — full CRM, automation, marketing control, account-wide workflow audit, live funnel-capture verification, and the only programmatic GHL workflow builder, now multi-tenant across client accounts.",
   "main": "dist/index.js",
   "bin": {
     "ghl-mcp": "dist/index.js"
@@ -16,7 +16,8 @@
     "templates/external-funnel/cloudflare-worker.js",
     "templates/external-funnel/README.md",
     "README.md",
-    "CHANGELOG.md"
+    "CHANGELOG.md",
+    "skills"
   ],
   "scripts": {
     "build": "esbuild src/index.ts --bundle --platform=node --target=node20 --format=cjs --outfile=dist/index.js --packages=external && esbuild src/capture-helper.ts --bundle --platform=node --target=node20 --format=cjs --outfile=dist/capture-helper.js --packages=external",

package/skills/blueprint/README.md

@@ -0,0 +1,27 @@
+# GHL Command Blueprint
+
+Blueprint turns a new client's intake into a complete, reviewable GoHighLevel build plan for that client's sub-account, then hands you two checklists: what GHL Command will build for you, and what you have to do yourself, in order. It plans. You approve. Nothing is built until you say so.
+
+v1 produces the reviewable build plan and the two-part checklist, and stops at the approval gate. One-shot auto-build is the next phase.
+
+## Install
+
+1. Unzip this so the folder lands at `~/.claude/skills/blueprint/` (with `SKILL.md` directly inside it).
+2. Restart Claude, or open a new session, so it loads the skill.
+3. Run it: say **"run Blueprint"** (or "build my Blueprint", or `/blueprint`).
+
+## Before you run it
+
+- **Be in the right account.** Blueprint plans against whatever GoHighLevel sub-account you are currently in. Point it at the new, empty client account and confirm it first.
+- **You need GHL Command** connected to your GoHighLevel.
+
+## What you get back
+
+- A build plan for the account: pipeline and stages, custom fields, tags, the intake form, a funnel outline, email and SMS sequences, and the workflows that wire them together.
+- Two checklists: what Blueprint will build automatically once you approve, and what only you can do in the GHL UI or with an outside service (A2P, Stripe, calendar, phone number, sending domain), in the order you need to do it.
+
+Every reference in the plan is a name, not a raw GoHighLevel ID. That is what stops the silent-failure bug where one dead ID skips every action under it and the workflow still shows green.
+
+## Funnels: GHL-native or your own site
+
+Each funnel can be built **inside GoHighLevel** (the default — zero setup on your part) or as a **custom site you host** on Cloudflare/Vercel and wire back to your GHL sub-account. The external path is for technically-capable users: you need your own host account + CLI, a GHL Private Integration token you store as a host secret, and comfort with a one-time command-line deploy. Blueprint generates the site, hands you the exact verified wiring values, and runs a live verification gate, but it never deploys for you or holds your keys. If that's not you, pick GHL-native and everything still works.

package/skills/blueprint/SKILL.md

@@ -0,0 +1,149 @@
+---
+name: blueprint
+description: Turn a GHL Command client intake into a complete, reviewable GoHighLevel account build plan — the GHL Command Blueprint. Detects Agency OS for a deeper brief (else uses the built-in intake form), selects an industry preset, generates a structured build plan (pipeline, fields, tags, calendar, form, funnel, email/SMS, workflows) with symbolic refs not real IDs, and renders a two-part approval checklist (what GHL Command builds automatically vs. what you must do manually, in order). The plan stops at the human approve gate; GHL-native staging then runs via apply_build_plan. Each funnel can be GHL-native (default) or an external site the user hosts (Cloudflare/Vercel) and wires back to GHL — a power-user, capability-gated lane that generates the site, injects verified field IDs, walks the user through their own deploy, and finishes only when verify_funnel passes on the real URL. Triggers on build my Blueprint, run Blueprint, GHL Command Blueprint, build a client account, watch it build a client, new client account, client onboarding build, build plan, account build spec, external funnel, host my own funnel.
+compatibility: Claude Code, Claude Cowork, Claude.ai
+---
+
+# GHL Command Blueprint (plan generation)
+
+You are a **senior GoHighLevel solutions architect**. You turn a client's intake into a complete, build-ready account plan — clean, minimal, every automation wired to fire, in the order it must be built so nothing references a dead ID. You have one professional obsession: the GHL silent-failure bug, where an action points at a pipeline, stage, field, or workflow whose ID no longer exists and GHL skips it and everything beneath it with no error and a workflow that still shows green. You design so that can never happen.
+
+This skill produces a **build plan** (the contract in `references/brief-schema.md` and `references/build-plan-schema.md`) and renders it for human review. It runs against whatever account `get_current_location` returns. **It does not execute anything in v1** — it stops at the approval gate. Execution (`apply_build_plan`) is phase 2, owned by the MCP.
+
+> Account-agnostic, always. No hardcoded IDs, no dependency on any specific agency's stack. The plan carries symbolic **refs** (`pipeline.main`, `stage.new_lead`), never real GHL IDs. The phase-2 executor resolves ref → id at build time, after each object is created and verified. That is what kills the silent-failure class.
+
+## The pipeline you run
+
+```
+Detect brief source ─► Source the brief (§2A) ─► Select preset ─► Fill skeleton ─► Derive handoffs ─► Generate copy ─► Assemble plan (per-funnel target) ─► Quality gate ─► Render approval view
+                                                                                                                              │
+   external funnel only, AFTER approval ──────────────────────────────────────────────────────────────────────────────────►│ stage GHL side (apply_build_plan) ─► generate + inject site ─► deploy preview→confirm→promote ─► verify_funnel gate ─► done
+```
+
+Read `references/preset-format.md` once; it defines the tokens (`{{...}}`), `conditionalOn`, `fillFrom`, and `copyDirection` you will resolve. Read `references/agency-os-detection.md` for the brief-source decision. Read `references/approval-view.md` for the final render. Read `references/external-funnel.md` only when a funnel is `target: "external"` (the capability gate + site gen/deploy + verify lane).
+
+---
+
+## STEP 1 — Detect the brief source (do this first, before any questions)
+
+Run the Agency OS detection in `references/agency-os-detection.md`:
+- **Detected** (skills `agency-os:*` present / `agency-os@agency-os` installed / artifacts on disk) → **offer (default yes)** to build the brief from Brand DNA / ICA / Offer. Ingest existing `owner-profile.md` / `ica-output.md` / offer output; if installed-but-not-run, offer to run/chain the `build-*` skills with one confirmation (never silent auto-run — they are interactive interviews); if declined, fall back.
+- **Not detected** → use the built-in intake question set, and surface the one-line credit to Agency OS by Muhammad Asmal (https://aileadbuilder.com).
+
+Business OS is a deferred second detection target — do not detect it yet.
+
+## STEP 2 — Source the brief (§4)
+
+**Partner-OS path:** ingest the Agency OS artifacts per the mapping in `references/agency-os-detection.md`. Carry the deep ICA / offer / brand-DNA structures **verbatim** in `brief.extended`. Set `briefSource: "agency_os"` (or `"hybrid"` if you also collect channel/tech facts Agency OS does not capture — booking/email/SMS/A2P/payment/calendar state). Always resolve those channel/tech facts somewhere, because they drive the handoffs.
+
+**Form path:** read the submission via `get_form_submissions_full` (the MCP installs the form from `references/intake-question-set.md`), or, if no submission exists yet, ask the §3 questions conversationally — only what changes the design, never a wall of questions. Normalize to the brief per the key→field map. Set `briefSource: "intake_form"`.
+
+Either way you end with a §4-conforming brief: `business`, `offer`, `audience`, `goal`, `channels`, `assets`, derived `flags`, and (partner-OS) `extended`. Do not emit `null` for unknowns — omit the field. Compute `flags`: `needs_a2p`, `stripe_not_connected`, `calendar_oauth_needed`, `email_domain_needed`.
+
+## STEP 3 — Select the preset
+
+Resolve in this order:
+1. If `brief.preset` is set, match it against each preset's `selectors.aliases`.
+2. Else match `brief.business.type` against `selectors.businessTypes`.
+3. Else use the library `default` preset (`med_spa`). (`generic` is the neutral fallback for clinic / coach / ecom / local-service / agency via its `businessTypes`; it is no longer the default.)
+
+Special case: if the brief describes a **time-boxed on-site event + database reactivation** (event dates, deposit + balance, package tiers, SMS reactivation of an existing list), select `clinic_launch_a2p` even if business_type would route elsewhere. When ambiguous, ask the operator which model fits; do not guess into the heavy compliance preset silently.
+
+Load the chosen preset's `skeleton`.
+
+## STEP 4 — Fill the skeleton (deterministic; see preset-format §"fill algorithm")
+
+Apply, in order:
+1. **Evaluate `conditionalOn`** on every item (and every workflow action). Drop where false. Prune refs that now dangle, and record each prune (you will note these in the summary, not silently drop).
+2. **Resolve `fillFrom`** lists. The main case is pipeline stages: if `goal.salesStages` is non-empty, build `stage.<slug>` refs from it in order; else use the preset `default`. If a workflow references a `stage.*` not in the chosen set, map it to the nearest equivalent (first stage for "new lead" creation) and note it — never ship a dead ref.
+3. **Substitute `{{tokens}}`** (with `||` fallback). Where a token resolves empty and has no fallback, omit the field and note the default you used.
+4. **Derive interest tags + field options** from the offer/business type (e.g. `interest-injectables` for a med spa) and add them to `tags` + the `field.interest` options, mirroring each other.
+
+## STEP 5 — Derive flag-driven handoffs
+
+Ensure the plan contains exactly the handoffs the brief calls for (the preset already declares the conditional ones; confirm and add any missing):
+- `needs_a2p` → `handoff.a2p` (blocks all SMS sends)
+- `stripe_not_connected` → `handoff.stripe`
+- `calendar_oauth_needed` → `handoff.calendar_oauth` (produces the booking link)
+- a calendar with `requiresStaff` and no known staff → `handoff.add_staff` (blocks the calendar)
+- `email_domain_needed` → `handoff.email_domain` (blocks email sends)
+
+Each handoff carries `owner` (**OPERATOR-UI** / **OPERATOR-EXT** / **TEAM** — customer-safe labels; never internal names. The MCP still accepts the legacy `JERRY-UI`/`JERRY-EXT`/`SASHA` and normalizes them, but EMIT the canonical ones), a precise `instruction`, a `successCheck`, and `blocks`. This is the honest "what GHL Command cannot do for you" layer; it is designed, not an afterthought.
+
+**A2P gating is workflow-level.** For `handoff.a2p`, `blocks` must list each SMS-bearing **workflow** ref (e.g. `workflow.speed_to_lead`) so those workflows stay DRAFT until A2P is met — a bare `sms.*` wildcard gates only the asset surface, not a workflow's publish state. List the SMS-bearing workflow refs plus the `sms.*` asset refs, and prune any that conditional drops removed.
+
+## STEP 6 — Generate copy (gated, grounded, editable)
+
+Default for REVIEW: **outlines** (`subject` + `bodyOutline` + `mergeTags` for emails; `bodyOutline` for SMS; `outline` for pages). Turn each `copyDirection` into a concrete outline grounded in `offer`, `audience`, and — when present — `extended` (voice from brandDna, angle from ICA, value-stack language from offer). Keep SMS A2P-safe (opt-out line; for the launch preset, avoid the forbidden-words list). See RATIFICATION §3 for the copy-depth policy.
+
+**Before execution, expand to full `body`.** A `send_email` / `send_sms` action whose asset carries only an outline (no `body`) is reported by `apply_build_plan` as `needsContent` and will NOT build. So any email/SMS that is actually SENT by a workflow must have a full `body` (not just `bodyOutline`) before you hand the plan to `apply_build_plan mode:"execute"`. Outlines are for the approval render; the sent assets get real copy. The worked example (`examples/medspa-build-plan.json`) ships the expanded `body` form — that is what dry-runs with 0 needs-content.
+
+## STEP 7 — Assemble the plan (§5)
+
+Emit a §5-conforming object: `schemaVersion`, `planId`, `briefId`, `preset`, `summary`, then the object arrays (`pipelines`, `customFields`, `tags`, `customValues`, `calendars`, `forms`, `funnels`, `emails`, `sms`, `workflows`, `handoffs`), `buildOrder`, and an empty `idMap`. Keep strictly to contract fields (the MCP validators may be strict). Record provenance (preset id + version, brief source) in the `summary` text, not as an extra field. Use GHL-correct enums: `dataType` ∈ {TEXT, LARGE_TEXT, NUMERICAL, PHONE, **MONETORY**, CHECKBOX, SINGLE_OPTIONS, MULTIPLE_OPTIONS, FLOAT, DATE, TEXTBOX_LIST, FILE_UPLOAD, SIGNATURE}; `calendarType` ∈ {round_robin, event, class_booking, collective, service_booking}.
+
+Workflow actions stay **logical** (type + key params + refs). Do not emit GHL-native action JSON — the executor expands logical actions via `action-schemas.json` and owns the failure-prone shapes (`internal_update_opportunity` node-level discriminator, `internal_notification`/task-notification nesting, `remove_from_workflow` dual id, `wait` `startAfter`, `attachments:[]`, `html` vs `body`, node `next`/`parentKey` chaining). All object pointers are refs. Max 40 actions per workflow; split longer flows into linked + exit workflows.
+
+**Triggers — use only native types** so they auto-build instead of falling through to a manual GHL-UI step: `contact_tag` (needs `tagRef`), `form_submission` (needs `formRef`), `appointment` (needs `appointmentStatus`: `confirmed`/`noshow`/`new`/`showed`/`cancelled`/`invalid`; `calendarRef` optional), `customer_reply`, `pipeline_stage_updated` (needs `pipelineRef`+`stageRef`), `inbound_webhook`, `payment_received`. `form_submitted`/`contact_replied` are accepted aliases, but `tag_added`/`appointment_status`/`appointment_booked` are NOT recognized and become manual steps — never emit them.
+
+**`internal_notification.to` needs a real GHL user id.** A non-user value builds `selectedUser:""` = notify-all, which GHL will not publish. Resolve the operator's user id from `get_users` on the current location at fill time (the preset carries the `{{operator.userId}}` token) and substitute it. With multiple users, ask whom to notify. If none can be resolved, leave it as a `TEAM` handoff rather than ship an unpublishable notify-all. This is the one place a real id legitimately appears in a plan (Blueprint never creates users).
+
+**Branching + appointment-relative actions.** `find_opportunity` is the only branching action and MUST be the last action in its workflow (its found/notFound branches do not rejoin). `wait_appointment` ("N before the appointment") only works in a workflow with an `appointment` trigger. The MCP validator enforces both, plus unique object names within each type and a 40-node cap (a workflow containing a `find_opportunity` branch cannot be auto-split).
+
+**Per-funnel target (GHL-native vs external).** For each funnel, set `target` ∈ `ghl` (default) / `external` (+ `host`/`domain` when external). Ask once per funnel: "Build this funnel inside GHL, or as a custom site you host on Cloudflare/Vercel and wire back to GHL?" The brief may pre-answer. **The instant a funnel is set to `external`, run the capability gate in `references/external-funnel.md` §1** — plainly state the required access (own host account + CLI, a GHL Private Integration token they store as a host secret, comfort with a one-time CLI deploy, optional domain/DNS) and say outright it is for technically-capable users; if that is not them, steer to `target: "ghl"`. Default GHL; never assume dev skills. The chosen target renders per funnel in the approval view (external = the power-user path, with ownership facts).
+
+## STEP 8 — Quality gate (run on yourself before showing anything)
+
+Re-read the plan as the person who has to build it tomorrow and score 1-10 on:
+1. Does every workflow have both a trigger and an exit (and do nurtures stop on response)?
+2. Does every ref resolve to an object defined in the plan, with a build order that creates targets before dependents? (No dangling refs after the prune step.)
+3. Is there anything in here the client will never use? (Cut it.)
+4. Is speed-to-lead genuinely fast and automatic?
+5. Does naming fit the client's industry and tier (from `business.type` and, if present, `extended`)?
+6. Is every step the MCP cannot truly one-shot represented as an explicit handoff with a success check (A2P, Stripe, OAuth, staff, email domain)?
+7. Do the enums match GHL (MONETORY spelling, calendarType values), so the plan will pass the MCP validators?
+
+If any score is below 9, fix it and re-score. Then proceed.
+
+## STEP 9 — Render the approval view (§5A)
+
+Render the two-part checklist per `references/approval-view.md`:
+1. **GHL Command will build this automatically** — every creatable object, grouped and counted, in plain English.
+2. **You must do these yourself, in this order** — every handoff, topologically ordered by `blocks`/`produces`, with owner, instruction, success check, and what it unblocks.
+
+Invite edits (rename / drop / reorder / adjust). Re-render after edits. End by stating plainly: nothing is built yet; the plan stops at approval. On approval, the GHL-native automatic list is staged via `apply_build_plan` — run `mode:"dry_run"` FIRST, show the two-part report, and only on the operator's go run `mode:"execute"`. A clean plan dry-runs with 0 `actionsNeedContent` and 0 unexpected `actionsManual` (the funnel page-content step and the declared handoffs are expected, not failures).
+
+**Workflows default to DRAFT — prompt before publishing.** `apply_build_plan` builds workflows DRAFT unless `publishWorkflows:true`. Before any workflow goes live, ASK the operator: "Publish these now, or leave them DRAFT for review?" Pass `publishWorkflows:true` only on an explicit yes. Workflows gated by an unmet handoff (e.g. SMS workflows behind `handoff.a2p`) never auto-publish even when opted in; pass satisfied handoffs in `metHandoffs` to lift their gate. If any funnel is `target: "external"`, also run STEP 10 after approval.
+
+## STEP 10 — External funnel lane (only if a funnel is `target: "external"`)
+
+For each external funnel, run the lane in `references/external-funnel.md` after approval. Summary:
+1. **Stage the GHL side.** Confirm the active sub-account, then `apply_build_plan` `mode:"dry_run"` → show the report → on the operator's go, `mode:"execute"`. Capture the returned `externalWiring` bundle (verified custom-field IDs, `bookingUrl`, trigger tag) and the speed-to-lead workflow id. If `externalWiring.unresolved` is non-empty, stop and re-run execute — never wire a form to an unresolved field.
+2. **Generate + inject the site.** Generate the site with `frontend-design` from the page outlines + brand. Inject the lead form keyed by the bundle's **verified `fieldId`s** (custom fields under `custom: {<fieldId>: value}`, never name-guessed; option values must match GHL option values), the `bookingUrl` into the booking CTA, a honeypot, and Turnstile for production. Fail closed (never a silent success).
+3. **Deploy — the user runs every command; the product deploys nothing and never handles the token.** Scaffold `wrangler.toml` (vars only); the user sets `GHL_PIT` as a host secret themselves. Deploy to a preview URL → confirm → promote to production. Never silently clobber a live deployment.
+4. **Verify, then call it done.** Run `verify_funnel` on the real branded production URL (built from the bundle: `funnelUrl` = the Worker URL, `triggerTag`, `workflowId`, `expectCustom` from the form fields, `consentFieldId` if messaging). The funnel is done ONLY when `verify_funnel` passes (backend contact truth + field-value fidelity + tag landed + workflow not DRAFT + outreach fired + consent + dedup), a real browser submit on the branded URL landed with correct field values, and a burner booking is confirmed. Otherwise say what failed and stop.
+
+---
+
+## Hard rules (do not violate)
+- No real GHL IDs in a plan, ever. Refs only.
+- No silent failures: every cross-reference resolves; every handoff has a success check; every prune is noted.
+- No fabricated specifics. Mark assumptions `[ASSUMPTION]` and unconfirmed facts `[UNVERIFIED]`. Never fabricate prices, stats, phone numbers, or claims.
+- Honest capability boundaries. Always show the steps only the operator can do. It makes the rest believable.
+- Operator voice. No em-dashes, no hype, no emoji-spam. Client-ready.
+- Do not clone or redistribute Agency OS / Business OS. Detect, integrate, credit.
+- The plan never executes itself. Stop at approval. After approval, GHL-native staging runs only via `apply_build_plan` (confirm the account first); the external funnel lane (STEP 10) runs only on an informed yes through the capability gate.
+- **External funnels are customer-managed, zero product involvement in their accounts.** The product generates, scaffolds, hands over verified wiring, and verifies — it never deploys for the user, never asks for or stores their token, never touches their host/GHL account beyond what the operator's own session does. The user owns hosting, the secret, uptime, and DNS.
+- **External forms send verified GHL custom-field IDs, never name-guessed keys** (the silent-drop class). A funnel is not "done" until `verify_funnel` passes on the real branded production URL plus a burner booking — never on a thank-you page.
+
+## Files in this skill
+- `references/intake-question-set.md` — the built-in §3 questions (also the source the MCP form installer reads).
+- `references/agency-os-detection.md` — §2A detect → offer → fallback + ingestion mapping.
+- `references/preset-format.md` — token / conditional / fill grammar + the deterministic fill algorithm.
+- `references/approval-view.md` — the §5A render spec + template.
+- `references/external-funnel.md` — the `target: "external"` lane: capability gate, site gen + verified-fieldId injection, user-run deploy (preview→confirm→promote), and the `verify_funnel`-gated finish. Read only when a funnel is external.
+- `presets/med-spa.preset.json` (+ `.md`) — the **default** reference preset (live-validated 2026-06-25).
+- `presets/generic-client.preset.json` (+ `.md`) — the neutral fallback preset (clinic / coach / ecom / local-service / agency; not default).
+- `presets/clinic-launch-a2p.preset.json` (+ `.md`) — the launch-event / A2P preset (not default).
+- `examples/` — the worked `medspa-*` brief → plan → approval view, with `medspa-dry-run-report.md` (the live proof: `validate_build_plan` valid + `apply_build_plan` dry_run clean). `sample-*` is the older generic-preset example.
+- `RATIFICATION.md` — the schema §7 decisions this skill is built on (#3 copy depth, #4 preset determinism, #9 ingest vs auto-run).

package/skills/blueprint/examples/medspa-approval-view.md

@@ -0,0 +1,92 @@
+# Build Plan — Glow Aesthetics
+
+A full lead-to-member account for your med spa: a pipeline that follows your own sales
+stages, the fields and tags to track every lead, a booking calendar, an A2P-compliant
+inquiry form and funnel, and a complete email + text follow-up system that stops the
+moment a client replies. Below is what GHL Command builds for you automatically, and the
+short list of things only you can do, in order.
+
+Generated from the **Med Spa** preset (v1.0.0) · brief source: intake_form · schema v0.1.
+This is a plan for your review. Nothing is built yet. Edit anything below, then approve.
+
+> Live-validated 2026-06-25: `validate_build_plan` → valid, 48 refs, 0 dead. `apply_build_plan`
+> dry_run → 40 objects, 28 actions auto-built, 0 needing copy, 0 needing a manual GHL step,
+> every workflow trigger auto-built. See [`medspa-dry-run-report.md`](medspa-dry-run-report.md).
+
+---
+
+## 1. GHL Command will build this automatically (once you approve)
+
+**Pipeline**
+- Build pipeline "Glow Aesthetics Patient Journey" with 7 stages: New Lead → Contacted → Consult Booked → Showed → Treated → Member / Rebooked → Lost.
+
+**Custom fields (5)**
+- Lead Source (dropdown)
+- Service Interest (multi-select: Injectables / Tox, Dermal Filler, Facials / Skin, Membership, Weight / Body)
+- Appointment Date (date)
+- Consult Deposit Paid (checkbox)
+- Estimated Lifetime Value (monetary)
+
+**Tags (17)**
+- Source: source-website, source-instagram, source-facebook, source-google, source-referral
+- Lifecycle: lifecycle-new-lead, contacted, consult-booked, showed, treated, member, lapsed, lost
+- Interest: interest-injectables, interest-filler, interest-facials, interest-membership
+
+**Custom values (1)**
+- Booking Link (filled after you connect your calendar — step 1 below)
+
+**Calendar**
+- "Glow Aesthetics Consultation" (round-robin, Mon-Fri 9-5 default — edit hours after build). Auto-assigned to you as the solo provider.
+
+**Form**
+- "Glow Aesthetics New Client Inquiry": First name, Last name, Email, Phone (required), plus Service Interest mapped to the custom field.
+
+**Funnel**
+- "Glow Aesthetics Lead Funnel": a Free Skin Assessment opt-in page (→ the inquiry form, with the A2P-compliant consent block) and a Thank You page (booking CTA). Page content is yours to fill from the funnel template — see Part 2.
+
+**Email + SMS assets**
+- 5 emails: Welcome / First Touch, Nurture / Education, Pre-Consult Reminder, No-Show Re-offer, Win-back.
+- 3 SMS: Speed-to-lead, Consult reminder, No-show rebook. _(Texts will not send until A2P is approved — step 2 below.)_
+
+**Workflows (5)** _(all build DRAFT; you choose when to publish)_
+- "Speed to Lead" — on inquiry → tag new lead, create opportunity at New Lead, send welcome email, alert you, wait 5 min, send a text. _(stops on reply; SMS held until A2P)_
+- "Lead Nurture" — for leads who don't book: wait 1 day, educate by email, wait 3 days, mark lapsed. _(stops on reply; email-only, publishes freely)_
+- "Replied - Stop and Route" — the moment a lead replies → pull them out of nurture, tag contacted, alert you.
+- "New Patient Onboarding" — on a confirmed appointment → stop the nurture, tag booked, move the opportunity to Consult Booked, send the pre-visit email, then text a reminder one day before the appointment. _(SMS held until A2P)_
+- "No-Show Win-back" — on a no-show → tag lapsed, alert you, send a re-offer email, then look up their opportunity: if one exists, move it back to Contacted and text a rebook nudge; if not, send the win-back email. _(SMS held until A2P)_
+
+_Total: 40 objects across 11 types — a full pipeline, 5 fields, 17 tags, a custom value, a calendar, a form, a funnel, 5 emails, 3 texts, and 5 workflows. 28 workflow actions auto-built._
+
+---
+
+## 2. You must do these yourself, in this order
+
+1. **Connect your calendar (Google / Outlook)** — **You (in GHL)**
+   - What: open the Glow Aesthetics Consultation calendar > Connections and authorize Google or Outlook, then copy the booking link into the Booking Link custom value.
+   - Why now: this is a login only you can approve, and it produces the Booking Link the emails and texts use.
+   - Done when: the calendar shows a connected account and the booking link resolves.
+
+2. **Register A2P 10DLC (so texts can send)** — **You (external: carrier)**
+   - What: submit your A2P brand and campaign through the GHL Trust Center. Save your submission package first.
+   - Why now: the Speed to Lead, Onboarding, and No-Show workflows stay DRAFT and their texts stay dark until A2P is approved (7-14 day review).
+   - Done when: the A2P campaign shows submitted/approved.
+
+3. **Design + populate your funnel pages** — **You (in GHL)**
+   - What: fill the opt-in and thank-you page content from the funnel template (`funnel-page-content-template.md`). The opt-in page MUST carry the A2P consent checkbox (not pre-checked), your legal business name + mailing address, and Privacy/Terms links.
+   - Why now: GHL Command builds the funnel and named steps; the page content and design are yours (and the A2P consent block must be present before A2P review).
+   - Done when: both pages are published with the required A2P, SEO, and FAQ elements.
+
+4. **Connect Stripe (to take payment)** — **You (external: Stripe)**
+   - What: connect Stripe in Payments > Integrations and create your consult-deposit and membership products.
+   - Why now: the funnel is built, but the money connection is yours to authorize.
+   - Done when: Stripe shows connected and your products exist.
+
+_Not included (not needed for this build): an email-domain step — your email sending is already set up._
+
+---
+
+_v1 stops here. When you approve, the automatic list above is ready for one-shot staging via
+`apply_build_plan` (confirm the account first). Each manual step is verified before the steps
+that depend on it run, so nothing is ever wired to something that does not exist yet. You
+will be asked, before any workflow goes live, whether to publish now or leave them DRAFT for
+review — they default to DRAFT._

package/skills/blueprint/examples/medspa-brief.json

@@ -0,0 +1,52 @@
+{
+  "schemaVersion": "0.1",
+  "briefId": "sub_medspa_demo",
+  "preset": "med_spa",
+  "briefSource": "intake_form",
+  "business": {
+    "name": "Glow Aesthetics",
+    "type": "med spa",
+    "website": "glowaesthetics.com",
+    "location": "Scottsdale, AZ",
+    "timezone": "America/Phoenix",
+    "teamSize": "Just me",
+    "monthlyLeadVolume": "100-500",
+    "hours": "Mon-Fri 9:00am-5:00pm"
+  },
+  "offer": {
+    "summary": "Injectables, dermal filler, and medical facials for first-time and returning clients, plus a membership for regulars.",
+    "pricePoints": [
+      { "name": "New client consult", "price": "19" },
+      { "name": "Tox session", "price": "350" },
+      { "name": "Glow Membership", "price": "149/mo" }
+    ],
+    "leadMagnet": "Free skin assessment",
+    "avgDealValue": "350"
+  },
+  "audience": {
+    "ideal": "Women 30-55 in North Scottsdale who want to look refreshed, not overdone",
+    "painPoints": ["early signs of aging", "not knowing who to trust with their face"],
+    "objections": ["price", "fear of looking overdone or fake"]
+  },
+  "goal": {
+    "primary": "book appointments",
+    "salesStages": ["New Lead", "Contacted", "Consult Booked", "Showed", "Treated", "Member / Rebooked", "Lost"],
+    "bookingNeeded": true,
+    "followUpStyle": "high-touch"
+  },
+  "channels": {
+    "email": true,
+    "sms": true,
+    "a2pStatus": "not started",
+    "payment": "Stripe not connected",
+    "calendarConnected": false,
+    "social": ["instagram", "facebook"]
+  },
+  "assets": {
+    "existingPipeline": "no",
+    "existingWorkflows": "",
+    "brand": "logo + navy/gold palette, domain ready",
+    "notes": "Solo operator for now; wants speed-to-lead and a no-show win-back."
+  },
+  "flags": ["needs_a2p", "stripe_not_connected", "calendar_oauth_needed"]
+}

package/skills/blueprint/examples/medspa-build-plan.json

@@ -0,0 +1,265 @@
+{
+  "schemaVersion": "0.1",
+  "planId": "plan_medspa_demo",
+  "briefId": "sub_medspa_demo",
+  "preset": "med_spa",
+  "summary": "Generated by the GHL Command Blueprint plan-gen skill from preset med_spa v1.0.0 (brief source: intake_form). Builds Glow Aesthetics a med-spa lead-to-member system: a 7-stage Patient Journey pipeline, lead-source/service-interest/appointment custom fields, source + lifecycle + interest tags, a round-robin consult calendar, an A2P-compliant intake form + lead funnel, a full email/SMS follow-up library, and five workflows (speed-to-lead, nurture, reply-route, confirmed-appointment onboarding with an appointment-relative reminder, and a no-show win-back that branches on whether an opportunity exists). SMS-bearing workflows are held DRAFT behind the A2P handoff; the booking link is filled by the calendar-connect handoff. internal_notification targets the operator's real GHL user id (resolved live via get_users at plan-gen time; shown here as a placeholder). Nothing is built until you approve.",
+  "pipelines": [
+    {
+      "ref": "pipeline.patient_journey",
+      "name": "Glow Aesthetics Patient Journey",
+      "stages": [
+        { "ref": "stage.new_lead", "name": "New Lead", "position": 0 },
+        { "ref": "stage.contacted", "name": "Contacted", "position": 1 },
+        { "ref": "stage.consult_booked", "name": "Consult Booked", "position": 2 },
+        { "ref": "stage.showed", "name": "Showed", "position": 3 },
+        { "ref": "stage.treated", "name": "Treated", "position": 4 },
+        { "ref": "stage.member", "name": "Member / Rebooked", "position": 5 },
+        { "ref": "stage.lost", "name": "Lost", "position": 6 }
+      ]
+    }
+  ],
+  "customFields": [
+    { "ref": "field.lead_source", "name": "Lead Source", "dataType": "SINGLE_OPTIONS", "model": "contact", "options": ["Website", "Instagram", "Facebook", "Google", "Referral", "Walk-in", "Other"] },
+    { "ref": "field.service_interest", "name": "Service Interest", "dataType": "MULTIPLE_OPTIONS", "model": "contact", "options": ["Injectables / Tox", "Dermal Filler", "Facials / Skin", "Membership", "Weight / Body"] },
+    { "ref": "field.appointment_date", "name": "Appointment Date", "dataType": "DATE", "model": "contact" },
+    { "ref": "field.consult_deposit_paid", "name": "Consult Deposit Paid", "dataType": "CHECKBOX", "model": "contact", "options": ["Deposit paid"] },
+    { "ref": "field.lifetime_value", "name": "Estimated Lifetime Value", "dataType": "MONETORY", "model": "contact" }
+  ],
+  "tags": [
+    { "ref": "tag.source_website", "name": "source-website" },
+    { "ref": "tag.source_instagram", "name": "source-instagram" },
+    { "ref": "tag.source_facebook", "name": "source-facebook" },
+    { "ref": "tag.source_google", "name": "source-google" },
+    { "ref": "tag.source_referral", "name": "source-referral" },
+    { "ref": "tag.lc_new_lead", "name": "lifecycle-new-lead" },
+    { "ref": "tag.lc_contacted", "name": "lifecycle-contacted" },
+    { "ref": "tag.lc_consult_booked", "name": "lifecycle-consult-booked" },
+    { "ref": "tag.lc_showed", "name": "lifecycle-showed" },
+    { "ref": "tag.lc_treated", "name": "lifecycle-treated" },
+    { "ref": "tag.lc_member", "name": "lifecycle-member" },
+    { "ref": "tag.lc_lapsed", "name": "lifecycle-lapsed" },
+    { "ref": "tag.lc_lost", "name": "lifecycle-lost" },
+    { "ref": "tag.interest_injectables", "name": "interest-injectables" },
+    { "ref": "tag.interest_filler", "name": "interest-filler" },
+    { "ref": "tag.interest_facials", "name": "interest-facials" },
+    { "ref": "tag.interest_membership", "name": "interest-membership" }
+  ],
+  "customValues": [
+    { "ref": "cv.booking_link", "name": "Booking Link", "value": "", "filledBy": "handoff.calendar_oauth" }
+  ],
+  "calendars": [
+    {
+      "ref": "calendar.consult",
+      "name": "Glow Aesthetics Consultation",
+      "calendarType": "round_robin",
+      "openHours": [
+        { "daysOfTheWeek": [1, 2, 3, 4, 5], "hours": [{ "openHour": 9, "openMinute": 0, "closeHour": 17, "closeMinute": 0 }] }
+      ],
+      "availabilityType": 0,
+      "requiresStaff": true
+    }
+  ],
+  "forms": [
+    {
+      "ref": "form.intake",
+      "name": "Glow Aesthetics New Client Inquiry",
+      "fields": [
+        { "type": "standard", "key": "first_name", "required": true },
+        { "type": "standard", "key": "last_name", "required": false },
+        { "type": "standard", "key": "email", "required": true },
+        { "type": "standard", "key": "phone", "required": true },
+        { "type": "custom", "fieldRef": "field.service_interest", "required": false }
+      ]
+    }
+  ],
+  "funnels": [
+    {
+      "ref": "funnel.main",
+      "name": "Glow Aesthetics Lead Funnel",
+      "target": "ghl",
+      "pages": [
+        {
+          "ref": "page.optin",
+          "name": "Free Skin Assessment",
+          "role": "optin",
+          "outline": "HERO: H1 'Your Free Skin Assessment at Glow Aesthetics' + one-line subhead (refreshed, natural results for women in North Scottsdale); primary CTA 'Book my free assessment' to form.intake; logo + hero image (alt text). QUOTABLE SUMMARY (GEO): 2-4 plain sentences an answer engine can lift: what the free skin assessment is, who it serves (women 30-55 in North Scottsdale), and the next step. VALUE: 3-5 outcome-led benefits (natural-looking injectables, filler, medical facials, a plan to your goals). SOCIAL PROOF: real testimonials/credentials only, else omit. CAPTURE FORM (A2P-compliant, MANDATORY): name + email + phone (clearly labeled) + a NOT-pre-checked SMS consent checkbox with the four disclosures (opt-out, HELP, msg&data rates, frequency); visible business legal name + mailing address; Privacy Policy and Terms links at the point of capture; Privacy Policy states SMS/phone data is not shared or sold. FAQ: 4-8 real Q/A with FAQPage JSON-LD. FOOTER: NAP + legal links. HEAD: one H1, <title> under 60 chars, meta description under 155, canonical, LocalBusiness + Service + FAQPage JSON-LD. Fill from templates/funnel-page-content-template.md.",
+          "formRef": "form.intake"
+        },
+        {
+          "ref": "page.thankyou",
+          "name": "Thank You",
+          "role": "confirmation",
+          "outline": "Confirmation message ('Your assessment request is in'); set the next-step expectation; embed the booking widget via cv.booking_link / calendar.consult so they can self-schedule now. Keep NAP + Privacy/Terms links in the footer. No new opt-in needed. Fill from templates/funnel-page-content-template.md (confirmation role).",
+          "calendarRef": "calendar.consult"
+        }
+      ]
+    }
+  ],
+  "emails": [
+    {
+      "ref": "email.welcome_1",
+      "name": "Welcome / First Touch",
+      "subject": "Your free skin assessment with Glow Aesthetics",
+      "body": "Hi {{contact.first_name}},\n\nThank you for requesting your free skin assessment with Glow Aesthetics. We help women in North Scottsdale look refreshed and natural with injectables, dermal filler, and medical facials.\n\nYour next step is simple: book your complimentary consult and we will map a plan to your goals, with no pressure. Pick a time that works for you here:\n\n{{custom_values.booking_link}}\n\nIf now is not the right time, just reply to this email and we will help.\n\nWarmly,\nThe Glow Aesthetics Team",
+      "mergeTags": ["contact.first_name"]
+    },
+    {
+      "ref": "email.nurture_1",
+      "name": "Nurture / Education",
+      "subject": "The difference between refreshed and overdone",
+      "body": "Hi {{contact.first_name}},\n\nThe most common worry we hear is simple: nobody wants to look done. The good news is that natural results are a matter of technique and restraint, not luck.\n\nAt your free assessment we look at your face as a whole, explain your options in plain language, and only recommend what actually moves your goals. You leave with a plan, whether or not you treat that day.\n\nWhen you are ready, your assessment is here:\n\n{{custom_values.booking_link}}\n\nWarmly,\nThe Glow Aesthetics Team",
+      "mergeTags": ["contact.first_name"]
+    },
+    {
+      "ref": "email.consult_reminder",
+      "name": "Pre-Consult Reminder",
+      "subject": "Your Glow Aesthetics consult is coming up",
+      "body": "Hi {{contact.first_name}},\n\nLooking forward to seeing you for your consult. A few quick notes so we make the most of your time:\n\n- Come with a clean face if you can, no makeup is needed.\n- Bring any questions about injectables, filler, or facials.\n- Plan for about 30 minutes.\n\nNeed to change your time? Reply to this email or use your booking link:\n\n{{custom_values.booking_link}}\n\nSee you soon,\nThe Glow Aesthetics Team",
+      "mergeTags": ["contact.first_name"]
+    },
+    {
+      "ref": "email.no_show",
+      "name": "No-Show Re-offer",
+      "subject": "We missed you, let us get you rebooked",
+      "body": "Hi {{contact.first_name}},\n\nWe had you down for a consult and you did not make it, which is completely okay. Life happens.\n\nYour free assessment is still open. Grab a new time whenever it suits you:\n\n{{custom_values.booking_link}}\n\nIf there is anything we can answer first, just reply.\n\nWarmly,\nThe Glow Aesthetics Team",
+      "mergeTags": ["contact.first_name"]
+    },
+    {
+      "ref": "email.winback",
+      "name": "Win-back",
+      "subject": "It has been a while, {{contact.first_name}}",
+      "body": "Hi {{contact.first_name}},\n\nIt has been a little while since we connected about your skin goals. If looking refreshed for the season is on your mind, now is a good time.\n\nYour complimentary assessment is still available, and our calendar fills up fast this time of year:\n\n{{custom_values.booking_link}}\n\nWarmly,\nThe Glow Aesthetics Team",
+      "mergeTags": ["contact.first_name"]
+    }
+  ],
+  "sms": [
+    {
+      "ref": "sms.speed_to_lead",
+      "name": "Speed-to-lead text",
+      "body": "Hi {{contact.first_name}}, it's Glow Aesthetics. Thanks for requesting your free skin assessment. Want me to hold a consult time for you? Reply STOP to opt out.",
+      "mergeTags": ["contact.first_name"]
+    },
+    {
+      "ref": "sms.consult_reminder",
+      "name": "Consult reminder text",
+      "body": "Hi {{contact.first_name}}, a quick reminder about your Glow Aesthetics consult tomorrow. Reply here if you need to change the time. Reply STOP to opt out.",
+      "mergeTags": ["contact.first_name"]
+    },
+    {
+      "ref": "sms.no_show",
+      "name": "No-show rebook text",
+      "body": "Hi {{contact.first_name}}, we missed you at Glow Aesthetics today. Your free assessment is still open, want a new time? Reply STOP to opt out.",
+      "mergeTags": ["contact.first_name"]
+    }
+  ],
+  "workflows": [
+    {
+      "ref": "workflow.speed_to_lead",
+      "name": "Speed to Lead",
+      "trigger": { "type": "form_submission", "formRef": "form.intake" },
+      "stopOnResponse": true,
+      "actions": [
+        { "type": "add_contact_tag", "tagRef": "tag.lc_new_lead" },
+        { "type": "create_opportunity", "pipelineRef": "pipeline.patient_journey", "stageRef": "stage.new_lead", "name": "{{contact.name}} - New Lead" },
+        { "type": "send_email", "emailRef": "email.welcome_1" },
+        { "type": "internal_notification", "to": "REPLACEwithGetUsersId", "title": "New lead", "body": "New inquiry from {{contact.first_name}} {{contact.last_name}}" },
+        { "type": "wait", "value": 5, "unit": "minutes" },
+        { "type": "send_sms", "smsRef": "sms.speed_to_lead" }
+      ]
+    },
+    {
+      "ref": "workflow.lead_nurture",
+      "name": "Lead Nurture",
+      "trigger": { "type": "contact_tag", "tagRef": "tag.lc_new_lead" },
+      "stopOnResponse": true,
+      "actions": [
+        { "type": "wait", "value": 1, "unit": "days" },
+        { "type": "send_email", "emailRef": "email.nurture_1" },
+        { "type": "wait", "value": 3, "unit": "days" },
+        { "type": "add_contact_tag", "tagRef": "tag.lc_lapsed" }
+      ]
+    },
+    {
+      "ref": "workflow.reply_route",
+      "name": "Replied - Stop and Route",
+      "trigger": { "type": "customer_reply" },
+      "stopOnResponse": false,
+      "actions": [
+        { "type": "remove_from_workflow", "workflowRef": "workflow.lead_nurture" },
+        { "type": "add_contact_tag", "tagRef": "tag.lc_contacted" },
+        { "type": "internal_notification", "to": "REPLACEwithGetUsersId", "title": "Lead replied", "body": "{{contact.first_name}} replied, follow up" }
+      ]
+    },
+    {
+      "ref": "workflow.onboarding",
+      "name": "New Patient Onboarding",
+      "trigger": { "type": "appointment", "appointmentStatus": "confirmed", "calendarRef": "calendar.consult" },
+      "stopOnResponse": false,
+      "actions": [
+        { "type": "remove_from_workflow", "workflowRef": "workflow.lead_nurture" },
+        { "type": "add_contact_tag", "tagRef": "tag.lc_consult_booked" },
+        { "type": "update_opportunity", "pipelineRef": "pipeline.patient_journey", "stageRef": "stage.consult_booked" },
+        { "type": "send_email", "emailRef": "email.consult_reminder" },
+        { "type": "wait_appointment", "value": 1, "unit": "days" },
+        { "type": "send_sms", "smsRef": "sms.consult_reminder" }
+      ]
+    },
+    {
+      "ref": "workflow.no_show",
+      "name": "No-Show Win-back",
+      "trigger": { "type": "appointment", "appointmentStatus": "noshow", "calendarRef": "calendar.consult" },
+      "stopOnResponse": true,
+      "actions": [
+        { "type": "add_contact_tag", "tagRef": "tag.lc_lapsed" },
+        { "type": "internal_notification", "to": "REPLACEwithGetUsersId", "title": "No-show", "body": "{{contact.first_name}} missed their consult" },
+        { "type": "send_email", "emailRef": "email.no_show" },
+        {
+          "type": "find_opportunity",
+          "pipelineRef": "pipeline.patient_journey",
+          "found": [
+            { "type": "update_opportunity", "pipelineRef": "pipeline.patient_journey", "stageRef": "stage.contacted" },
+            { "type": "send_sms", "smsRef": "sms.no_show" }
+          ],
+          "notFound": [
+            { "type": "send_email", "emailRef": "email.winback" }
+          ]
+        }
+      ]
+    }
+  ],
+  "handoffs": [
+    {
+      "ref": "handoff.calendar_oauth",
+      "owner": "OPERATOR-UI",
+      "title": "Connect your calendar (Google / Outlook)",
+      "trigger": "goal.bookingNeeded == true && channels.calendarConnected == false",
+      "instruction": "In the sub-account, open the Glow Aesthetics Consultation calendar > Connections and authorize your Google or Outlook account. This login can only be approved by you. Then copy the booking link into the Booking Link custom value.",
+      "produces": "cv.booking_link",
+      "successCheck": "Calendar shows a connected external account and the booking link resolves",
+      "blocks": ["cv.booking_link"]
+    },
+    {
+      "ref": "handoff.a2p",
+      "owner": "OPERATOR-EXT",
+      "title": "Register A2P 10DLC (so texts can send)",
+      "trigger": "channels.sms == true",
+      "instruction": "Submit your A2P brand and campaign through the GHL Trust Center / your carrier. The SMS steps are built but stay DRAFT and will not send until this is approved. Save your full submission package before submitting.",
+      "produces": null,
+      "successCheck": "A2P campaign status shows submitted or approved",
+      "blocks": ["workflow.speed_to_lead", "workflow.onboarding", "workflow.no_show", "sms.speed_to_lead", "sms.consult_reminder", "sms.no_show"]
+    },
+    {
+      "ref": "handoff.stripe",
+      "owner": "OPERATOR-EXT",
+      "title": "Connect Stripe (to take payment)",
+      "trigger": "channels.payment != 'Stripe connected'",
+      "instruction": "Connect Stripe under Payments > Integrations and create your consult-deposit and membership products. The funnel is built; authorizing the money connection is yours to do.",
+      "produces": null,
+      "successCheck": "Stripe shows connected and products exist",
+      "blocks": []
+    }
+  ],
+  "buildOrder": ["tag.*", "field.*", "cv.*", "pipeline.*", "calendar.*", "form.*", "funnel.*", "email.*", "sms.*", "workflow.*"],
+  "idMap": {}
+}