@sellable/install 0.1.101 → 0.1.102

package/bin/sellable-install.mjs

@@ -646,6 +646,25 @@ data, compare sources by source volume, sampled ICP fit, activity/warmth
 signals, cleanup risk, and confidence basis. If a user asks for a forecast,
 label it explicitly as not estimated from this run.
 
+Before any provider prompt, search, source scout, or signal-discovery call,
+show a short source-plan gate and ask for approval. The gate should say:
+
+- given this campaign, the viable source options
+- the recommended first lane
+- why that lane fits the buyer, offer, and likely public activity
+- what will be tested next
+- the fallback lane if relevant posts or ICP engagement look thin
+- that approval authorizes scouting/search only, not lead import or sending
+
+If active prospects likely engage with relevant LinkedIn content, recommend
+LinkedIn post engagement / Signal Discovery and name the post themes you will
+look for. If the niche is too private, low-volume, or unlikely to have relevant
+public posts, recommend Sales Nav recent activity, broader Sales Nav role/title
+filters, or Prospeo, and explain the tradeoff. Do not call \`search_signals\`,
+\`search_sales_nav\`, \`search_prospeo\`, \`fetch_post_engagers\`, or provider-scoped
+subagents until the user approves this source plan or explicitly chooses a
+different source.
+
 For campaign-attached Signal Discovery sampling, promote/select the exact posts
 with \`select_promising_posts\` before \`fetch_post_engagers\` so the user can see
 which posts are being sampled in the watched app. The watch guide should say
@@ -943,15 +962,19 @@ updates.
    queue workflow cells, attach a sequence, or start until filter choice is
    resolved, rubrics are saved when filters are enabled, template/token rules
    are approved on the default Use Template path, and the approved message set
-   is synced into the campaign brief. After rubrics save, pause and say the fit
-   rules are saved; approve the message template next; after approval, queue the
-   bounded review-batch \`enrichCellId\` cells to kick off enrichment/filtering.
+   is synced into the campaign brief. When filters are approved, immediately
+   call \`mcp__sellable__update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })\`
+   so the watched app moves to Filter Rules while rubrics are drafted/saved.
+   After rubrics save, pause and say the fit rules are saved; approve the
+   message template next; after approval, queue the bounded review-batch
+   \`enrichCellId\` cells to kick off enrichment/filtering.
    Product Generate Message cells must not run from the background template
    path before that template/token approval. AI Generated uses the
    product's AI-generated path and cancels or ignores the background template
    draft.
 6. The main thread owns watch navigation: use \`filter-choice\` after the 15-row
-   review batch, \`messages\` for the Use Template / AI Generated mode choice,
+   review batch, \`create-icp-rubric\` as soon as filters are approved,
+   \`messages\` for the Use Template / AI Generated mode choice,
    \`auto-execute-messaging\` for approved message work or the product's
    AI-generated path, and \`awaiting-user-greenlight\` for the final handoff.
    \`validate-sample\` is recovery/legacy only if reached.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.101",
+  "version": "0.1.102",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {

package/skill-templates/create-campaign.md

@@ -117,6 +117,25 @@ data, compare sources by source volume, sampled ICP fit, activity/warmth
 signals, cleanup risk, and confidence basis. If a user asks for a forecast,
 label it explicitly as not estimated from this run.
 
+Before any provider prompt, search, source scout, or signal-discovery call,
+show a short source-plan gate and ask for approval. The gate should say:
+
+- given this campaign, the viable source options
+- the recommended first lane
+- why that lane fits the buyer, offer, and likely public activity
+- what will be tested next
+- the fallback lane if relevant posts or ICP engagement look thin
+- that approval authorizes scouting/search only, not lead import or sending
+
+If active prospects likely engage with relevant LinkedIn content, recommend
+LinkedIn post engagement / Signal Discovery and name the post themes you will
+look for. If the niche is too private, low-volume, or unlikely to have relevant
+public posts, recommend Sales Nav recent activity, broader Sales Nav role/title
+filters, or Prospeo, and explain the tradeoff. Do not call `search_signals`,
+`search_sales_nav`, `search_prospeo`, `fetch_post_engagers`, or provider-scoped
+subagents until the user approves this source plan or explicitly chooses a
+different source.
+
 When the user has not supplied a source and multiple source angles are viable,
 scout those angles as independent branches when the host can actually do it:
 LinkedIn Engagement / active post engagers (internal `signal-discovery`
@@ -577,9 +596,12 @@ updates.
    queue workflow cells, attach a sequence, or start until the filter choice is
    resolved, rubrics are saved when filters are enabled, template/token rules
    are approved on the default Use Template path, and the approved message set
-   is synced into the campaign brief. After rubrics save, pause and say the fit
-   rules are saved; approve the message template next; after approval, queue the
-   bounded review-batch `enrichCellId` cells to kick off enrichment/filtering.
+   is synced into the campaign brief. When filters are approved, immediately
+   call `mcp__sellable__update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })`
+   so the watched app moves to Filter Rules while rubrics are drafted/saved.
+   After rubrics save, pause and say the fit rules are saved; approve the
+   message template next; after approval, queue the bounded review-batch
+   `enrichCellId` cells to kick off enrichment/filtering.
    Product Generate Message cells must not run from the background template
    path before that template/token approval.
    Do not ask the user to approve the brief before shell creation unless they
@@ -588,8 +610,9 @@ updates.
    `mcp__sellable__update_campaign({ campaignId, currentStep })` before major
    visible work so the user can watch progress in the app: `create-offer` for
    the brief, `pick-provider` or the selected provider step while sourcing,
-   `filter-choice` after the 15-row review batch, `messages` for the Use
-   Template / AI Generated mode choice, `auto-execute-messaging` for approved
+   `filter-choice` after the 15-row review batch, `create-icp-rubric` as soon
+   as filters are approved, `messages` for the Use Template / AI Generated mode
+   choice, `auto-execute-messaging` for approved
    message work or the product's AI-generated path, `awaiting-user-greenlight`
    for the final handoff, `settings` for sender selection, `sequence` after
    sender attach, and `send` once the recommended sequence is attached.