@sellable/install 0.1.154 → 0.1.155

package/agents/post-find-leads-filter-scout.md

@@ -12,17 +12,22 @@ Required inputs:
 
 - `campaignId`
 - campaign revision or `campaignUpdatedAt`
-- campaign brief content
+- campaign brief summary from the parent, then the current campaign brief loaded
+  through Sellable tools
 - selected source decision and provider/list state
 - `selectedLeadListId`
 - `workflowTableId`
-- initial campaign-table execution slice rows, including row ids/hash when available
+- compact initial campaign-table execution-slice basis: copied source row count,
+  review-batch row count, and review-batch basis/hash. Do not require the
+  parent to paste every row id when scoped row tools are available.
 - filter choice
 
 Required first steps:
 
 1. Verify the campaign/source/table ids from the parent thread match the live
-   campaign context.
+   campaign context. Read current campaign/table state and the review batch
+   through scoped Sellable tools such as `get_campaign`, `get_campaign_context`,
+   and `get_rows_minimal({ tableId: workflowTableId })`.
 2. Load the filter-leads reference before designing rubrics:
    `get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "references/filter-leads.md" })`.
 3. Treat campaign state and the campaign-table execution slice as the input of record.
@@ -33,6 +38,9 @@ Owned outputs:
 - Durable campaign rubrics via `save_rubrics({ campaignOfferId, leadScoringRubrics })`
   when the filter is confirmed and production-shaped rubrics are safe to write.
   `save_rubrics` is the durable writer.
+- If `save_rubrics` is unavailable in the branch, return production-shaped
+  `leadScoringRubrics` and mark `save_rubrics` as not yet persisted so the
+  parent can save them before filter approval.
 - concise filter/rubric summary returned to the parent thread
 
 Do not write or modify local markdown/json artifacts. Durable output is only

package/agents/registry.json

@@ -159,10 +159,10 @@
       "target": "filter-leads",
       "inputs": [
         "campaignId",
-        "campaignBrief",
+        "campaignBrief summary plus branch-loaded current campaignBrief",
         "source decision and selectedLeadList/source state",
         "workflowTableId",
-        "imported review-batch rows"
+        "compact review-batch count/hash or branch-loaded review rows"
       ],
       "producesArtifacts": [],
       "optionalProducesArtifacts": [],
@@ -187,6 +187,9 @@
         "tools": [
           "mcp__sellable__get_subskill_prompt",
           "mcp__sellable__get_subskill_asset",
+          "mcp__sellable__get_campaign",
+          "mcp__sellable__get_campaign_context",
+          "mcp__sellable__get_rows_minimal",
           "mcp__sellable__save_rubrics"
         ]
       }

package/package.json

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

package/skill-templates/create-campaign.md

@@ -421,15 +421,19 @@ Treat host capabilities as concrete functions, not prose conventions:
   not call it in the normal create-campaign source path.
 - `load_post_find_leads_scout_registry`: call
   `mcp__sellable__get_post_find_leads_scout_registry({})` after source
-  import and before dispatching Message Drafting only.
+  import and before dispatching Prospect Filters / Message Drafting.
+- `launch_prospect_filters`: Claude Code uses `Task` with `subagent_type`
+  `post-find-leads-filter-scout` when filters are chosen; Codex uses the
+  returned compatibility agent. Prospect Filters must save or return production
+  rubrics before message review can proceed.
 - `launch_message_drafting`: Claude Code uses `Task` with `subagent_type`
   `post-find-leads-message-scout` when listed; Codex uses the returned
   compatibility agent or a generic `gpt-5.5` / `xhigh` Message Drafting agent.
 
 If a required interactive question function or MCP loader is missing, stop and
-explain the Sellable install/reload problem. Source and filter work use
-product-native MCP orchestration in the parent; the only normal background
-branch is Message Drafting.
+explain the Sellable install/reload problem. Source work uses product-native MCP
+orchestration in the parent; the only normal post-import background branches are
+Prospect Filters and Message Drafting.
 
 Never narrate local draft housekeeping to the user. If you create directories,
 save drafts, write artifacts, or persist intermediate state, translate it into
@@ -745,7 +749,14 @@ updates.
    copies of this file; packaged Claude Code and Codex runs must use the MCP
    asset loader so they share the same config.
 3. Follow that prompt and workflow config exactly.
-4. For message generation, keep the parent thread as a lean orchestrator and
+4. For filter and message setup, keep the parent thread as a lean orchestrator.
+   When filters are chosen, use `post-find-leads-filter-scout` for Prospect
+   Filters and `post-find-leads-message-scout` for Message Drafting. The parent
+   waits for Prospect Filters first, verifies `save_rubrics` succeeded or saves
+   returned production rubrics itself, asks filter approval, and only then joins
+   Message Drafting for template review. When filters are skipped, launch only
+   Message Drafting.
+5. For message generation, keep the parent thread as a lean orchestrator and
    use the `post-find-leads-message-scout` compatibility agent for Message
    Drafting whenever the host exposes it
    and the current host policy allows agent launch. The worker must load
@@ -770,18 +781,19 @@ updates.
    synthesize local validation artifacts from general knowledge. The handoff to
    Message Drafting should pass compact basis only, not a long row-id list; the
    branch loads current brief/table rows and validation assets itself.
-5. Create the campaign shell early with the v1 brief so the user can open the
+6. Create the campaign shell early with the v1 brief so the user can open the
    watch link and see useful setup state immediately. Materialize the approved
    source list, copy confirmed rows into the campaign, and internally process the
    first campaign-table execution slice after the source is attached to the
    campaign; do not load prospect-setup registries/prompts before asking add
-   filters vs skip filters. Once the user answers, launch only Message Drafting
-   from the same campaign/table basis. If filters are approved, do filter/rubric
-   work inline in the parent thread. Do not queue workflow cells, attach a
+   filters vs skip filters. Once the user answers, launch Prospect Filters plus
+   Message Drafting when filters are chosen, or only Message Drafting when
+   filters are skipped. Do not queue workflow cells, attach a
    sequence, or start until saved filters and the
    message template/token rules are approved. When filters are chosen, 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.
+   so the watched app moves to Filter Rules while Prospect Filters drafts/saves
+   rubrics.
    After rubrics save, keep Filter Rules visible for approval; after approval,
    move to Filter Leads and show `Filters saved + waiting for message approval`
    until the template is approved.