@sellable/mcp 0.1.74 → 0.1.75

package/package.json

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

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

@@ -456,11 +456,22 @@ should test for this campaign. Those can run in parallel and usually take
   message quality gate outputs between `message-validation.md` and
   `approval-packet.md`.
 - Run the dependency chain as a DAG: `create-campaign-brief` -> `find leads`;
-  once `lead-review.md` and `lead-sample.json` exist, run `filter leads` and
-  `message generation` from the same basis (`brief.md`, `lead-review.md`,
-  `lead-sample.json`). Approval waits for both `lead-filter.md` and
-  `message-validation.md`, then reconciles that the selected message basis rows
-  still pass the final filter.
+  once `lead-review.md` and `lead-sample.json` exist, the normal path is the
+  `post-lead-workstreams` step. Launch `filter leads` and `message generation`
+  from the same basis (`brief.md`, `lead-review.md`, `lead-sample.json`) as
+  separate workstreams when the host supports real subagents/background work.
+  In Claude Code, use two Task/Agent subagents in the same assistant message;
+  in Codex, use disjoint worker subagents when the host exposes them. The
+  existing `filter-rubric` and `message-generation` steps remain focused retry
+  and resume targets.
+- Message generation does not need `lead-filter.md` to start. The moment
+  `lead-sample.json` exists with at least 5 probable good-fit rows and the lead
+  source is confirmed or auto-confirmed, start the message-generation
+  workstream from `brief.md`, `lead-review.md`, and `lead-sample.json`. It can
+  prepare proof inventory, token strategy, and candidate angles while
+  filter-leads tightens keep/exclude rules. Approval still waits for both
+  `lead-filter.md` and `message-validation.md`, then reconciles that the
+  selected message basis rows still pass the final filter.
 - `lead-sample.json` from `find leads` is always the message sample source.
   `filter leads` must not create a different message sample or cause message
   generation to fetch new prospects. The filter only marks which find-leads

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

@@ -548,10 +548,106 @@
         "auto_continue"
       ],
       "transitions": {
-        "lead_review_confirmed": "filter-rubric",
+        "lead_review_confirmed": "post-lead-workstreams",
         "revise_leads": "find-leads",
-        "confirm_with_user": "filter-rubric",
-        "auto_continue": "filter-rubric"
+        "confirm_with_user": "post-lead-workstreams",
+        "auto_continue": "post-lead-workstreams"
+      },
+      "interruptOnly": true
+    },
+    {
+      "id": "post-lead-workstreams",
+      "label": "Post-lead filter and message workstreams",
+      "normalFlow": true,
+      "onEnter": [
+        {
+          "action": "launch_post_lead_workstreams",
+          "mode": "parallel_when_host_supports_subagents",
+          "branches": [
+            {
+              "name": "filter-leads",
+              "target": "filter-leads",
+              "inputs": ["brief.md", "lead-review.md", "lead-sample.json"],
+              "producesArtifacts": ["lead-filter.md"],
+              "optionalProducesArtifacts": ["rubric.json"],
+              "ownership": "lead quality, false-positive patterns, keep/exclude rules, and production rubric translation only"
+            },
+            {
+              "name": "message-generation",
+              "target": "generate-messages",
+              "mode": "DRY MODE",
+              "inputs": ["brief.md", "lead-review.md", "lead-sample.json"],
+              "producesArtifacts": ["message-validation.md"],
+              "optionalProducesArtifacts": [
+                "message-prep.md",
+                "message-candidate-drafts.md"
+              ],
+              "ownership": "proof inventory, token strategy, angle drafting, skeptical-prospect review, and selected winner only"
+            }
+          ],
+          "earlyMessageStartRule": "As soon as lead-sample.json exists with at least 5 probable good-fit rows and the lead source is confirmed or auto-confirmed, launch message-generation from brief.md, lead-review.md, and lead-sample.json. Do not wait for lead-filter.md to begin proof inventory, token planning, or candidate angles.",
+          "finalMessageReconcileRule": "message-validation.md may start before lead-filter.md exists, but before message-review it must cite only lead-sample.json rows that still pass lead-filter.md. If the selected winner depends on a row later excluded by lead-filter.md, revise message-generation before message review.",
+          "claudeRule": "In Claude Code, launch both workstreams with Task/Agent subagents in the same assistant message when Task is available. Do not run filter first and then message generation unless subagents/background work are unavailable.",
+          "codexRule": "In Codex, launch disjoint worker subagents for filter-leads and message-generation when the host exposes subagents for this run. If the host cannot spawn them, run the same branches sequentially and say so.",
+          "fallback": "If real parallel branches are unavailable, run filter-leads and then message-generation in the parent thread. Do not claim background or parallel work in that fallback."
+        },
+        {
+          "action": "wait_for_post_lead_artifacts",
+          "requiredArtifacts": ["lead-filter.md", "message-validation.md"],
+          "optionalArtifacts": [
+            "rubric.json",
+            "message-prep.md",
+            "message-candidate-drafts.md"
+          ],
+          "reconciliationRule": "Before entering message-review, verify lead-filter.md and message-validation.md both came from the same brief.md, lead-review.md, and lead-sample.json. lead-filter.md gates the sample rows; lead-sample.json remains the message sample source."
+        }
+      ],
+      "requiredArtifacts": ["brief.md", "lead-review.md", "lead-sample.json"],
+      "producesArtifacts": ["lead-filter.md", "message-validation.md"],
+      "optionalProducesArtifacts": [
+        "rubric.json",
+        "message-prep.md",
+        "message-candidate-drafts.md"
+      ],
+      "allowedTools": [
+        "get_subskill_prompt",
+        "get_subskill_asset",
+        "Task",
+        "spawn_agent",
+        "AskUserQuestion",
+        "request_user_input"
+      ],
+      "toolRules": [
+        "The post-lead workstreams are disjoint: filter-leads owns lead-filter.md/rubric.json; message-generation owns message-validation.md/message-prep.md/message-candidate-drafts.md.",
+        "message-generation can start before lead-filter.md, but message-review cannot start until both lead-filter.md and message-validation.md exist and reconcile against the same lead-sample.json.",
+        "Do not let filter-leads create a new message sample. Do not let message-generation fetch new prospects.",
+        "Before writing message-validation.md, message-generation must read 100% of the real generate-messages prompt via chunked get_subskill_prompt({ subskillName: \"generate-messages\", offset, limit }) calls."
+      ],
+      "doNotAllow": [
+        "create_campaign",
+        "save_rubrics",
+        "import_leads",
+        "confirm_lead_list",
+        "update_campaign",
+        "queue_cells",
+        "start_campaign",
+        "check_rubric",
+        "generate_messages"
+      ],
+      "watchRequired": false,
+      "waitFor": [
+        "post_lead_workstreams_ready",
+        "revise_leads",
+        "revise_rubric",
+        "revise_messaging",
+        "confirm_with_user"
+      ],
+      "transitions": {
+        "post_lead_workstreams_ready": "message-review",
+        "revise_leads": "find-leads",
+        "revise_rubric": "filter-rubric",
+        "revise_messaging": "message-generation",
+        "confirm_with_user": "message-review"
       },
       "interruptOnly": true
     },

package/skills/generate-messages/SKILL.md

@@ -66,8 +66,11 @@ Use this mode when the caller explicitly says `DRY MODE`, `Phase 84`,
 `create-campaign-v2`, or provides:
 
 - `brief.md`
-- `lead-filter.md`
 - `lead-sample.json`
+- `lead-filter.md` when available. In the create-campaign-v2
+  `post-lead-workstreams` step, message generation may start before
+  `lead-filter.md` exists so it can prepare proof inventory, token strategy,
+  and candidate angles while filter-leads runs.
 
 Required dry-mode contract:
 
@@ -78,12 +81,20 @@ Required dry-mode contract:
 - do not call `mcp__sellable__update_campaign_brief`
 - do not mutate DB-backed campaign state
 - do not fetch fresh web or LinkedIn research
-- use only `brief.md`, `lead-filter.md`, and `lead-sample.json`
+- use only `brief.md`, `lead-sample.json`, and `lead-filter.md` when present
 - treat `lead-sample.json` from find-leads as the message sample source; do not
   ask filter-leads for a new sample, create a new sample, or fetch additional
   prospects for dry-mode message generation
-- use `lead-filter.md` only to decide which find-leads sample rows remain valid
-  for the final winner and which false-positive patterns must be avoided
+- if `lead-filter.md` is not present yet, do the expensive early work only:
+  proof inventory, token rules, strategy map, candidate angle drafting, and
+  provisional sample fills. Prefer writing `message-prep.md` and
+  `message-candidate-drafts.md` while waiting for the filter branch.
+- use `lead-filter.md` once available to decide which find-leads sample rows
+  remain valid for the final winner and which false-positive patterns must be
+  avoided
+- do not mark `message-validation.md` as final or ready for message review until
+  `lead-filter.md` exists and the selected winner cites only rows that still
+  pass the filter
 - generate 2-3 sample messages inline
 - write findings to `message-validation.md`
 - start `message-validation.md` with `Mode: DRY MODE (no DB mutation)`
@@ -98,9 +109,11 @@ Dry mode validates message quality before campaign mint.
 Read:
 
 - `brief.md`
-- `lead-filter.md`
 - `lead-sample.json` from the find-leads step; this is the only allowed sample
   source for dry-mode message generation
+- `lead-filter.md` when present. If it is absent because the caller launched
+  post-lead workstreams in parallel, start the prep/candidate stages and then
+  reconcile before final `message-validation.md`.
 - `mcp/sellable/skills/create-campaign-brief/references/phase75-active-runtime-message-pack.md`
 - `mcp/sellable/skills/create-campaign-v2/references/validation-criteria.md`
 - `mcp/sellable/skills/create-campaign-v2/references/thomas-revision-filters.md`