@sellable/mcp 0.1.98 → 0.1.100

package/dist/tools/prompts.js

@@ -319,7 +319,7 @@ export function listSubskillPrompts(limit, includePublic, includeInternal) {
     };
 }
 function markSubskillPromptLoaded(subskillName) {
-    if (subskillName === "create-campaign") {
+    if (subskillName === "create-campaign" || subskillName === "create-campaign-v2") {
         markCreateCampaignPromptLoaded();
     }
     if (subskillName === "research") {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.98",
+  "version": "0.1.100",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign/SKILL.md

@@ -341,6 +341,25 @@ lookup if it has not already run, then ask the campaign setup questions. The
 setup questions should use the confirmed company context so they do not feel
 generic.
 
+### Sufficient Intake Bypass
+
+When the user's invocation or first answer already supplies the campaign
+identity plus enough strategy context to draft the campaign, do not turn that
+into an interview. Treat setup as complete when the request contains:
+
+- identity or client/company context;
+- target prospects or buyer segment;
+- offer / CTA;
+- proof or claims to use / avoid;
+- lead-source preference, supplied list, or permission to find people.
+
+In that case, do one lightweight identity/company lookup, summarize the inferred
+direction in one or two lines, and immediately draft the campaign brief. Do not
+ask the buyer, offer, proof, or lead-source setup questions again unless a
+required field is missing, the supplied inputs conflict, or the campaign focus is
+genuinely ambiguous. It is fine to include an explicit assumption line in the
+brief; the approval gate lets the user revise it.
+
 Before the identity gate, use this customer-facing shape:
 
 ```text

package/skills/create-campaign-v2/SKILL.md

@@ -234,6 +234,15 @@ Optional debug/UAT draft directory, disabled in normal customer runs:
   company page is available, do not pass it as `senderLinkedinUrl`. If a
   `clientProspectId` is available, pass that instead.
 
+  Sufficient-intake bypass: when the invocation or first operator answer already
+  supplies identity/client context, target prospects, offer/CTA, proof guidance,
+  and lead-source preference or permission to find people, do not ask the setup
+  packet again. Do one lightweight lookup, state the inferred campaign direction
+  in one or two lines, and move directly into the campaign brief. Ask only when a
+  required field is missing, the supplied inputs conflict, or the campaign focus
+  is genuinely ambiguous. The brief approval gate is the correction point for
+  inferred assumptions.
+
   After the user confirms the campaign identity, check whether the company
   context implies more than one campaignable product line, service, or offer.
   If so, ask one structured campaign-focus question before the setup packet
@@ -290,6 +299,10 @@ Optional debug/UAT draft directory, disabled in normal customer runs:
   confirmed, the setup packet must
   use the structured question gate and ask buyer, offer/CTA, proof, and lead
   source. All four questions must include an `Other / custom` option.
+  Exception: if the initial request already satisfies the sufficient-intake
+  bypass above, skip the setup packet and draft the brief from the supplied
+  context. Do not ask first-turn setup questions just to restate choices the
+  operator already provided.
 - After the founder answers the first strategy/source packet, explain the next
   stage only: campaign brief creation and brief approval. Use this shape:
 

package/skills/create-campaign-v2/core/flow.v2.json

@@ -170,10 +170,30 @@
           "fallback": "If WebSearch is unavailable, use available MCP profile/company/post tools, call complete_sender_research with observed counts, and carry explicit proof gaps into the setup packet.",
           "chatRenderRule": "Use researched company positioning and proof options in the buyer/offer/proof/source setup packet; do not ask generic strategy questions from company name alone."
         },
+        {
+          "action": "skip_strategy_packet_when_initial_context_is_sufficient",
+          "when": "after_identity_lookup_before_founder_strategy_source_packet",
+          "condition": "initial invocation or first operator answer includes identity/client context, target prospects, offer/CTA, proof guidance, and lead-source preference or permission to find people",
+          "requiredCoveredFields": [
+            "identity_or_client_context",
+            "target_prospects",
+            "offer_or_cta",
+            "proof_guidance",
+            "lead_source_preference_or_find_people_permission"
+          ],
+          "effect": "mark founder_strategy_source_packet_answered and proceed to render_post_intake_progress_preamble without asking setup questions again",
+          "askOnlyWhen": [
+            "a required covered field is missing",
+            "the supplied inputs conflict",
+            "the campaign focus is genuinely ambiguous"
+          ],
+          "chatRenderRule": "State the inferred campaign direction in one or two lines and draft the brief. Do not ask buyer, offer, proof, or source setup questions just to restate information the operator already supplied; the brief approval gate is the correction point."
+        },
         {
           "action": "ask_source_intake_after_strategy_batch",
           "artifact": "lead-source-intake.json",
           "optional": true,
+          "skipWhen": "skip_strategy_packet_when_initial_context_is_sufficient matched",
           "question": "How should we get the people for this campaign?",
           "options": [
             "Find people for me (recommended if you don't already have your own list)",