From this morning's brief (2026-10-31)

Open the whole brief

← all clients

CC

Chile Colonial live scale-up rebuilt Sat, Oct 31, 1:20 PM

Shared growth plan — 2026-09-21 through 2026-10-20. reported revenue $9,946.84; reported net $1,431.45.

PROVISIONAL — reported net is not a verified contribution margin; reconcile itemized costs and refunds. The reconciliation difference is $35.07.

Chile Colonial: 0 execution result(s) recorded in the last 7 days; 4 overdue action(s). Financial or evidence gaps remain. See Growth plan for current actions and evidence. The separate Numbers tab is an earlier planning snapshot; it does not establish that today's profit target is met or authorize increased spending.

The machineall 5 of the things we run for them are up to date
Changes madenothing has been changed on their account in this run
Work delivered37 things produced in the last 30 days
Results measurednothing scored yet - the first one finishes its waiting period on Nov 3
Waiting on you23 things cannot move until you decide or hand something over

Growth plan

Grow profitable revenue and contribution toward this client's sourced milestone, using one measured growth driver at a time.

30-day, 60-day and quarterly scorecard

Plan as of 2026-09-13. Baseline: July · COULD-NOT-VERIFY — baseline source missing or changed.

Reported revenue 8797.79; reported net 1512.89. Reported net is not certified contribution. Source window, fees, cost coverage and client-specific adjustments must reconcile before financial scoring. This snapshot does not refresh the underlying data. Evidence review 2026-09-13: August US reported revenue $10022.01, net $2267.56. Drive COGS export and live Sellerboard both leave B07QSSCQ9S (SKU 010 and VR-JWNH-0EVY) without costs. Do not apply the condiment jar cost to this oil three-pack. Existing cost-coverage gate remains open. Evidence: Sync/client-growth/scorecards/financial-evidence-20260913/CC-observation.json. August settlement review starts September 15; original baseline values remain unchanged.

Baseline source and limits

mode7-analysis/mode6k-actuals/CC_actuals.json

[]

Horizon / deadlineMeasurable targetOwner / existing actionsResults / evidence
30 days
2026-09-09 → 2026-10-08
Review: 2026-10-09		Reconcile the current Chile Colonial window and Amazon sessions; isolate B07QSSCQ9S until both SKU/channel cost rows are documented.

Delivery target: 1 source-backed delivery (validated_baseline_and_selected_intervention_package)

mode6k + client-growth
CC-ECONOMICS, CC-RISK, CC-DIAGNOSIS, CC-EXPERIMENT, CC-TIKTOK-LANE-A-LIVE		OVERDUE — outcome not assessed

UNMEASURED — experiment measurement is separate from milestone delivery

CC-ECONOMICS: blocked · Preparation / research

Stopped run reconciled; unfinished action is eligible for safe resume

No usable completion evidence

CC-RISK: completed · Preparation / research

Completed the CC read-only risk deliverable. Current SP-API stock/restock coverage spans all 19 FBA ASINs; three offer states are explicitly unmeasured. Protective exceptions are three zero-supply ASINs and the expired 2026-09-01 insurance policy; the existing pending COI request was preserved without duplication. No account or price changes were made.

No usable completion evidence

CC-DIAGNOSIS: open · Preparation / research

No result recorded

No usable completion evidence

CC-EXPERIMENT: open · Preparation / research

No result recorded

No usable completion evidence

CC-TIKTOK-LANE-A-LIVE: in_progress · Preparation / research

record

No usable completion evidence

Evidence requiredOne client-specific package: dated cost/fee/traffic bridge with unknowns; verified stock/offer constraints; one Mode6K-selected lever, own-unit success measure, owner and due date. Record the actual implementation evidence separately. A blocked prerequisite is a miss/hold, not a successful intervention.
60 days
2026-09-09 → 2026-11-07
Review: 2026-11-09		Restore the sourced monthly contribution milestone using costed Chile Crunch products and one verified driver.

Delivery target: 1 source-backed delivery (matched_window_intervention_assessment)

Financial working target: 2000 USD contribution per month. EXISTING KPI WORKING TARGET — validate current basis. Maintain or recover the existing milestone; no new growth percentage or spending allowance is assumed.

mode6k + client-growth
CC-ECONOMICS, CC-DIAGNOSIS, CC-EXPERIMENT, CC-WEEKLY		OPEN — outcome not assessed

UNMEASURED — experiment measurement is separate from milestone delivery

CC-ECONOMICS: blocked · Preparation / research

Stopped run reconciled; unfinished action is eligible for safe resume

No usable completion evidence

CC-DIAGNOSIS: open · Preparation / research

No result recorded

No usable completion evidence

CC-EXPERIMENT: open · Preparation / research

No result recorded

No usable completion evidence

CC-WEEKLY: open · Preparation / research

No result recorded

No usable completion evidence

Evidence requiredOne assessment links the chosen lever to baseline and follow-up windows, live implementation proof and the appropriate client profit/royalty measure. Record achieved, missed or inconclusive with source evidence. A planning document or low sample is not proof of lift.
Quarterly
2026-10-01 → 2026-12-31
Review: 2027-01-15		Hold profitable demand through Q4 with measured stock cover and a separate evidence-based TikTok readout.

Delivery target: 1 source-backed delivery (settled_quarter_outcome_and_next_quarter_plan)

Financial working target: 2000 USD contribution per month. EXISTING KPI WORKING TARGET — validate current basis. Maintain or recover the existing milestone; no new growth percentage or spending allowance is assumed.

mode6k + horizon-review
CC-WEEKLY, CC-EXPERIMENT, CC-TIKTOK-LANE-A-LIVE		OPEN — outcome not assessed

UNMEASURED — experiment measurement is separate from milestone delivery

CC-WEEKLY: open · Preparation / research

No result recorded

No usable completion evidence

CC-EXPERIMENT: open · Preparation / research

No result recorded

No usable completion evidence

CC-TIKTOK-LANE-A-LIVE: in_progress · Preparation / research

record

No usable completion evidence

Evidence requiredOne Q4 assessment after settlement compares October–December actuals to the validated goal, separates recurring contribution from recoveries, records held/missed milestones, and assigns Q1 actions and inventory needs. Monthly reference targets are not multiplied into an invented quarter forecast.

Inputs and delivery deadlines

External due dates are agency follow-up/review deadlines, not promises made by the client.

CC-INPUT-20260913 · overdue · due 2026-09-18

Cost remains blank for chili oil three-pack B07QSSCQ9S, SKUs 010 and VR-JWNH-0EVY, in both the Drive sheet and live Sellerboard; verify remaining SKU effective dates and settled fees.

Owner: Chile Colonial cost owner. Agency coordinator: mom-report + mode6k. Action: CC-ECONOMICS.

Read Sync/client-growth/scorecards/financial-evidence-20260913/CC-observation.json and its hashed underlying sources, then resolve only the remaining input on CC-ECONOMICS by 2026-09-18. Existing client correspondence is the source request; do not duplicate it. Retain account holds and source-date/settlement gates.

Close only when: Re-exported cost table has documented costs on both rows and the own-client bridge explains the bounded cost uncertainty.

Latest cycle (2026-10-26T12:01:37.151Z): needs_reconciliation — A process receipt is not work evidence

Financial targets are existing contract references pending the stated validation; these dates do not change spending authority. Quarterly actuals are assessed after settlement.

Weekly progress

COULD-NOT-MEASURE · As of 2026-10-26T12:01:37.016Z

Chile Colonial: 0 execution result(s) recorded in the last 7 days; 4 overdue action(s). Financial or evidence gaps remain.

Reporting window: from: 2026-09-21; through: 2026-10-20

MetricReported value
revenue9946.84
orders291
units297
ad Spend1582.12
reported Net1431.45
tacos Pct15.91
reconciliation Difference35.07

PROVISIONAL — reported net is not a verified contribution margin; reconcile itemized costs and refunds.

No period comparison is available.

What changed

No changes have been recorded.

Open issues

  • Reported net has an unexplained $35.07 difference from the displayed revenue/cost lines.
  • Executor needs_reconciliation: A process receipt is not work evidence
  • Codex audit COULD-NOT-MEASURE: The supplied artifact confirms a read-only needs_input handoff, but no new evidence resolves the repeated open-audit findings. Required underlying source files, current reuse justification, terminal action state, owner receipt, and closure reconciliation are absent or truncated.
  • 39 Codex audit(s) have unresolved findings; inspect audit evidence before dependent work.

Next actions

  • Verify current financial bridge and SKU economics — blocked — 2026-09-13 — Read existing dependency and execution evidence from Sync/client-growth/runs/CC/index.json before starting; preserve completed/partial effects. Client CC only. Read the canonical registry, KPI contract and current client requests/stock holds. Resolve this client by CODE CC and the Ludwig login. Chile Colonial is the account/Sellerboard name; Chile Crunch is the product line. Refresh the source period before interpreting economics. Collect same-window P&L, itemized fees/refunds, costed SKU identity and COGS coverage. Reconcile contribution vs posted net and fixed costs. Use the client's own source and enumerate missing input rows; do not replace unknowns with averages. Save the input body/hash/window and reproducible calculation. Keep target references provisional until validated.
  • Select one evidence-backed growth or loss-recovery driver — open — 2026-09-16 — Read existing dependency and execution evidence from Sync/client-growth/runs/CC/index.json before starting; preserve completed/partial effects. Client CC only. Read the canonical registry, KPI contract and current client requests/stock holds. Resolve this client by CODE CC and the Ludwig login. Chile Colonial is the account/Sellerboard name; Chile Crunch is the product line. Refresh the source period before interpreting economics. Use ECONOMICS and RISK evidence plus own search-query/conversion/ads history. Rank opportunities by verified contribution potential, stock feasibility, effort and confidence; select one driver. For ads-only work use royalty efficiency. Keep discovery findings attached to existing actions; do not create duplicate campaigns/listings or change prices.
  • Prepare a measurable, bounded intervention for the chosen driver — open — 2026-09-19 — Read existing dependency and execution evidence from Sync/client-growth/runs/CC/index.json before starting; preserve completed/partial effects. Client CC only. Read the canonical registry, KPI contract and current client requests/stock holds. Resolve this client by CODE CC and the Ludwig login. Chile Colonial is the account/Sellerboard name; Chile Crunch is the product line. Refresh the source period before interpreting economics. Design the selected intervention at unchanged prices. Record a fresh immutable baseline window, own-unit forecast, spend/resource cap supported by verified economics, stop rule, rollback, matched post-intervention readout and confounders. Research and staging only. List exact gate evidence required before any account change; preserve parked/launch restrictions.
  • Publish client progress, unresolved inputs and next actions — open — 2026-09-11 — Read existing dependency and execution evidence from Sync/client-growth/runs/CC/index.json before starting; preserve completed/partial effects. Client CC only. Read the canonical registry, KPI contract and current client requests/stock holds. Resolve this client by CODE CC and the Ludwig login. Chile Colonial is the account/Sellerboard name; Chile Crunch is the product line. Refresh the source period before interpreting economics. Review plan execution and audit outcomes. Prepare actual-versus-target reference with matching periods, evidence-backed completed work, unknowns and next priority; distinguish descriptive financial movement from causal lift and report operator interventions/time where measured.
  • Daily client decisions, execution and outcome review — blocked — Run today's operating review for CC only. Read this client's current goals, financial contract, stock/launch holds, requests, action history, independent audit findings and previous measured results. Reconcile earlier changes and existing skill/lever ownership before doing anything. Use fresh authoritative evidence where needed; reuse still-valid evidence with its date. Choose and implement the highest-value justified non-price work through existing skills, including protective corrections, advertising optimization, catalog/conversion work or recovery within this client's established limits. Missing costs or permissions gate only the affected action: keep working on safe supported actions. Never unpark ads, increase approved total spend, change prices or override stock holds without the separately required client authority. Record exact before-state, payload, after-state, rollback limits, expected benefit and measurement date for every change. If no change is justified, record the evidence-based reason. Address due weekly/monthly/quarterly work within this same cycle and retain its existing action IDs. For a decision only the operator can supply, save operator-requests.json as an array with what, why, expectedBenefit, blockingReason and evidence paths; state the exact choice and scope, not a vague approval request. Keep independent audit findings visible for re-review. Record useful partial work before the runtime deadline.

Latest execution: codex — needs_reconciliation — horizon-CC-2026-q3.

  • claude — blocked
  • codex — failed — A process receipt is not work evidence
Weekly evidence and sources
facts
source: C:\Users\miraf\projects\mode6-catalog-gap-audit\inputs_CC\CC_ProfitAndLoss_2026-09-21_2026-10-20.csv; period: from: 2026-09-21; through: 2026-10-20; modified At: 2026-10-21T07:18:04.614Z
evidence
Not recorded
execution Evidence
C:\Users\miraf\Sync\client-growth\runs\CC\2026-10-26T11-50-32.774Z-24d8bbd9\horizon-CC-2026-q3-examination-20261026T1200Z.md
source Path
Not recorded

Codex audit

COULD-NOT-MEASURE — The supplied artifact confirms a read-only needs_input handoff, but no new evidence resolves the repeated open-audit findings. Required underlying source files, current reuse justification, terminal action state, owner receipt, and closure reconciliation are absent or truncated.

Pending: 70. Coverage is limited to registered work and supplied evidence.

Actions and next steps

ActionOwnerStatusDueNext action
Reconcile current client priorities, prior work and constraintsclient-growth + mode6k + ppc-recapcompleted2026-09-11Read existing dependency and execution evidence from Sync/client-growth/runs/CC/index.json before starting; preserve completed/partial effects. Client CC only. Read the canonical registry, KPI contract and current client requests/stock holds. Resolve this client by CODE CC and the Ludwig login. Chile Colonial is the account/Sellerboard name; Chile Crunch is the product line. Refresh the source period before interpreting economics. Read current client documents, action/lever history and unresolved tasks; deduplicate completed work and identify existing owners. Produce a client-specific priority and constraint map with explicit unresolved requests. Do not send messages or change accounts.
Verify current financial bridge and SKU economicsmom-report + catalog-econ + mode6kblocked2026-09-13Read existing dependency and execution evidence from Sync/client-growth/runs/CC/index.json before starting; preserve completed/partial effects. Client CC only. Read the canonical registry, KPI contract and current client requests/stock holds. Resolve this client by CODE CC and the Ludwig login. Chile Colonial is the account/Sellerboard name; Chile Crunch is the product line. Refresh the source period before interpreting economics. Collect same-window P&L, itemized fees/refunds, costed SKU identity and COGS coverage. Reconcile contribution vs posted net and fixed costs. Use the client's own source and enumerate missing input rows; do not replace unknowns with averages. Save the input body/hash/window and reproducible calculation. Keep target references provisional until validated.
Verify saleable stock, offers and account risksinventory-replenish + amazon-featured-offer + mode10-daily-checkcompleted2026-09-13Read existing dependency and execution evidence from Sync/client-growth/runs/CC/index.json before starting; preserve completed/partial effects. Client CC only. Read the canonical registry, KPI contract and current client requests/stock holds. Resolve this client by CODE CC and the Ludwig login. Chile Colonial is the account/Sellerboard name; Chile Crunch is the product line. Refresh the source period before interpreting economics. Read current saleable/reserved/inbound stock, velocity and stock-hold instructions; inspect offer/account/catalog risks and prior repairs. Check existing claims before proposing another. Save dated current evidence and separate protective work from optional growth; no account mutations.
Select one evidence-backed growth or loss-recovery drivermode6 + mode6k + mode7-strategyopen2026-09-16Read existing dependency and execution evidence from Sync/client-growth/runs/CC/index.json before starting; preserve completed/partial effects. Client CC only. Read the canonical registry, KPI contract and current client requests/stock holds. Resolve this client by CODE CC and the Ludwig login. Chile Colonial is the account/Sellerboard name; Chile Crunch is the product line. Refresh the source period before interpreting economics. Use ECONOMICS and RISK evidence plus own search-query/conversion/ads history. Rank opportunities by verified contribution potential, stock feasibility, effort and confidence; select one driver. For ads-only work use royalty efficiency. Keep discovery findings attached to existing actions; do not create duplicate campaigns/listings or change prices.
Prepare a measurable, bounded intervention for the chosen drivermode6k + client-growth + self-checkopen2026-09-19Read existing dependency and execution evidence from Sync/client-growth/runs/CC/index.json before starting; preserve completed/partial effects. Client CC only. Read the canonical registry, KPI contract and current client requests/stock holds. Resolve this client by CODE CC and the Ludwig login. Chile Colonial is the account/Sellerboard name; Chile Crunch is the product line. Refresh the source period before interpreting economics. Design the selected intervention at unchanged prices. Record a fresh immutable baseline window, own-unit forecast, spend/resource cap supported by verified economics, stop rule, rollback, matched post-intervention readout and confounders. Research and staging only. List exact gate evidence required before any account change; preserve parked/launch restrictions.
Publish client progress, unresolved inputs and next actionsclient-growth + mode6kopen2026-09-11Read existing dependency and execution evidence from Sync/client-growth/runs/CC/index.json before starting; preserve completed/partial effects. Client CC only. Read the canonical registry, KPI contract and current client requests/stock holds. Resolve this client by CODE CC and the Ludwig login. Chile Colonial is the account/Sellerboard name; Chile Crunch is the product line. Refresh the source period before interpreting economics. Review plan execution and audit outcomes. Prepare actual-versus-target reference with matching periods, evidence-backed completed work, unknowns and next priority; distinguish descriptive financial movement from causal lift and report operator interventions/time where measured.
Daily client decisions, execution and outcome reviewclient-growthblockedNot recordedRun today's operating review for CC only. Read this client's current goals, financial contract, stock/launch holds, requests, action history, independent audit findings and previous measured results. Reconcile earlier changes and existing skill/lever ownership before doing anything. Use fresh authoritative evidence where needed; reuse still-valid evidence with its date. Choose and implement the highest-value justified non-price work through existing skills, including protective corrections, advertising optimization, catalog/conversion work or recovery within this client's established limits. Missing costs or permissions gate only the affected action: keep working on safe supported actions. Never unpark ads, increase approved total spend, change prices or override stock holds without the separately required client authority. Record exact before-state, payload, after-state, rollback limits, expected benefit and measurement date for every change. If no change is justified, record the evidence-based reason. Address due weekly/monthly/quarterly work within this same cycle and retain its existing action IDs. For a decision only the operator can supply, save operator-requests.json as an array with what, why, expectedBenefit, blockingReason and evidence paths; state the exact choice and scope, not a vague approval request. Keep independent audit findings visible for re-review. Record useful partial work before the runtime deadline.
TikTok → Amazon: Attribution tags live on every TikTok destination, first clicks measuredtiktok-shop-opsin_progressNot recordednode ~/.claude/skills/tiktok-shop-ops/tools/seed_calc.mjs --client CC --asin <hero ASIN> --price <client price> --out ~/Sync/client-growth/evidence/CC/tiktok-seed-calc-2026-09-11.md; then amazon-attribution dormant-tag repair (tiktok_<creator>_<sku> tags), creator briefs via influencer-creator-ops Stage 1–3, organic calendar via organic-social-content; record each step with --evidence

30-day plan and quarterly roadmap

First 30 days
label: First 30 days; from: 2026-09-09; through: 2026-10-08; priority: Establish current client economics and constraints, resolve input blockers, and stage one measurable driver.

Starting figures and what we still cannot measure

status
NOT-VERIFIED-FOR-ROLLOUT
source
C:\Users\miraf\Sync\client-growth\onboarding\CC\sources.json
note
Archived actuals are evidence references, not a current financial baseline; ECONOMICS validates its own window and quality.

Targets

status
CONTRACT-REFERENCE-REQUIRES-CURRENT-VALIDATION
financial Authority
mode6k/kpi_contracts.json clients.CC
contract
status: DERIVED (2026-08-03) - live trailing-90d; posture: scale-up; targets: cm dollars monthly: 2000; tacos ceiling: 0.378; provenance: DERIVED - M1 sized from June peak (net $2,009); tacos_ceiling = BE-ACoS 37.8% (workbook, COGS present). Flag for operator amendment; milestone ladder: name: M0 true landed break-even; metric: cm_dollars_monthly; value: 0; sized from: ACHIEVED - all 3 months positive; name: M1 net >= $2,000/mo (restore+hold June peak); metric: cm_dollars_monthly; value: 2000; sized from: June 2026 actual $2,009; July dipped to $1,527 - reachable in 1-2 cycles; active milestone: 1
goal Id
CC-CONTRIBUTION
new Growth Target
Not recorded
reason
No new client revenue promise inferred during onboarding.
next Input
Refresh own same-window economics and verify the active milestone before sizing a new growth target.

Rules for spending and scaling

1
No price, discount, coupon, shipping-charge or repricer changes. No messages, purchases or client-account mutations from these research actions.
2
Preserve existing client instructions and inventory/advertising holds; absence of a copied constraint is not authorization to ignore its source.
3
Resolve this client by CODE CC and the Ludwig login. Chile Colonial is the account/Sellerboard name; Chile Crunch is the product line. Refresh the source period before interpreting economics.
4
Never infer causal lift or time saved from completed tasks; use the experiment ledger and independent evidence review.
5
OPERATOR SCOPE 2026-09-13: LMS/Ludwig may receive necessary non-price listing/SEO changes outside titles, bullets and descriptions. Do not change item_name/title, bullet_point/bullets or product_description/description. Preserve these live fields exactly in every payload. Backend keywords, typed attributes and other supported fields remain eligible subject to existing client limits, evidence, ownership and verification.

Who does the work and checks it

cadence
daily: Shared all-client daily fleet schedule, America/Lima
engine
claude
fallback
codex
live Execution
true
automatic Actions
7
total Actions
8

Plan source: C:\Users\Brian\Sync\client-growth\plans\CC.json. Completed work and business results require dated evidence; planned actions do not prove results.

What I am working on — 20

  1. $37 a month raised 11 days ago

    ME — opening or answering a case with Amazon is already signed off, one at a time

    Open the FBA reimbursement case for CC in Seller Central for 2 Lost units (004-FBA B012TZUT7W 1, 013 fba B08KHPTBVL 1) and 3 net Unknown-Event units (Hot-2-FBA B0CHBH22WD 2, Variety-4-FBA B0CHBDMCHS 1) before the claim window closes.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. It is usually spend that produced nothing, a fee charged wrongly, or stock Amazon owes for. This one is worth $37 a month.

    the evidence behind it
    CC Sept 2026 ledger: 2 lost + 3 net unknown = 5 units x 7.48 avg COGS (CC_verified.json) = 37.42 one-time at cost

    Tracked: on the task board at https://app.clickup.com/t/z8y71x0hfq · finding ledgereom-CC-2026-09-lost-unreconciled.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ledgereom-CC-2026-09-lost-unreconciled --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ledgereom-CC-2026-09-lost-unreconciled --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ledgereom-CC-2026-09-lost-unreconciled --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  2. not sized raised 27 days ago

    ME — changing bids, budgets and campaigns is already signed off — I fire one, re-read it live, then do the rest

    Search-term and placement audit on the Sep spend increase; cut non-converting terms back to Aug spend level.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Sep vs Aug (gate-verified out/CC_verified.json): ad spend $1,330 vs $1,185 (+$145), sales $9,223 vs $10,022 (-8%), TACoS 14.4% vs 11.8%, net $1,745 vs $2,268 (-$522). Added spend did not buy sales.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyz14 · finding mom-CC-spend-up-sales-down-2026-09.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mom-CC-spend-up-sales-down-2026-09 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mom-CC-spend-up-sales-down-2026-09 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mom-CC-spend-up-sales-down-2026-09 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  3. $20 a month raised 3 days ago

    ME — the hidden search terms are not the wording customers read, so they are mine

    'lao gan ma chili crisp' is ALREADY being bid on in the ads (EXACT). Do NOT add it again — the shortfall is bid, placement or relevance, not coverage. Look at what it is winning and decide whether to raise the bid.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is worth $20 a month.

    the evidence behind it
    [KPI M1 net >= $2,000/mo (restore+hold June peak) | cm_dollars_monthly>=2000 | posture scale-up] MODE 6 engine, source report SQP: 'lao gan ma chili crisp' (vol 185): 28 purchases per week, brand share 0.00% -> $20/mo at stake (CONFIRMED). Action: 'lao gan ma chili crisp' is ALREADY being bid on in

    Tracked: NOT on the task board — nothing is chasing it but this row · finding mode6-cc-non-branded-capture-term-lao-gan-ma-chili-crisp.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode6-cc-non-branded-capture-term-lao-gan-ma-chili-crisp --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode6-cc-non-branded-capture-term-lao-gan-ma-chili-crisp --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode6-cc-non-branded-capture-term-lao-gan-ma-chili-crisp --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  4. not sized raised 34 days ago

    ME — changing bids, budgets and campaigns is already signed off — I fire one, re-read it live, then do the rest

    Verify what drove the purchase-share recovery on "chili crisp" and consider pressing via the conquest ladder before the monthly strategy review.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    mode-7-comp: purchase_share 1.18% Jul to 0.5% Aug to 0.62% Sep (RECOVERY, from market_share_flags_2026-09.md).

    Tracked: on the task board at https://app.clickup.com/t/z8y71wxw7y · finding cc-chili-crisp-purchase-share-2026-09.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-chili-crisp-purchase-share-2026-09 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-chili-crisp-purchase-share-2026-09 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-chili-crisp-purchase-share-2026-09 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  5. not sized raised 6 days ago

    ME — changing bids, budgets and campaigns is already signed off — I fire one, re-read it live, then do the rest

    run the competitor-identification pass on keywords 'chili crunch' and 'chili crisp', name who took the share, and attach it to this finding before the monthly strategy review decides the bid. Purchase share chili crunch 1.36% to 0.77%; chili crisp click share 0.86% to 0.53%, purchase share 0.64% to 0.45%.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Action: run the competitor-identification pass on keywords 'chili crunch' and 'chili crisp', name who took the share, and attach it to this finding before the monthly strategy review decides the bid. Purchase share chili crunch 1.36% to 0.77%; chili crisp click share 0.86% to 0.53%, purchase share 0

    Tracked: on the task board at https://app.clickup.com/t/z8y71x32ea · finding share-cc-chili-crisp-crunch-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-cc-chili-crisp-crunch-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-cc-chili-crisp-crunch-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-cc-chili-crisp-crunch-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  6. not sized raised 6 days ago

    ME — changing bids, budgets and campaigns is already signed off — I fire one, re-read it live, then do the rest

    run the competitor-identification pass on the CC share-shift keywords ("chili crunch" purchase_share 1.36%->0.77%, "chili crisp" click_share 0.86%->0.53%) listed in drift_findings_latest.md, name who took the share, and attach it to this finding before the monthly strategy review decides the bid. Unsized.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Action: run the competitor-identification pass on the CC share-shift keywords ("chili crunch" purchase_share 1.36%->0.77%, "chili crisp" click_share 0.86%->0.53%) listed in drift_findings_latest.md, name who took the share, and attach it to this finding before the monthly strategy review decides the

    Tracked: on the task board at https://app.clickup.com/t/z8y71x32u0 · finding drift-mshare-cc-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id drift-mshare-cc-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id drift-mshare-cc-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id drift-mshare-cc-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  7. 45 visits a month raised 37 days ago

    ME — catalog details, images and settings are mine — the four things customers read are not

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 45 visits a month — that is not dollars.

    the evidence behind it
    [CLICK] "chili onion crunch" wk ending 2026-09-19: impr share 7.2% -> click share 0.0% -> cart 0.0% -> purchase share 0.0% (market 38 purchases/wk, ours 0; 4 ASIN(s) pulled). Failing 3 of the last 3 weeks. Worth ~10.4 clicks/wk at share parity with the stage before. Source: SP-API SQP (sqp_funnel_ga

    Tracked: on the task board at https://app.clickup.com/t/86eyxq1w4 · finding sqp-funnel-cc-chili-onion-crunch-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-onion-crunch-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-onion-crunch-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-onion-crunch-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  8. 36 visits a month raised 23 days ago

    ME — catalog details, images and settings are mine — the four things customers read are not

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 36 visits a month — that is not dollars.

    the evidence behind it
    [CLICK] "lao gan ma spicy chili crisp" wk ending 2026-10-03: impr share 1.7% -> click share 0.2% -> cart 0.0% -> purchase share 0.0% (market 122 purchases/wk, ours 0; 6 ASIN(s) pulled). Failing 3 of the last 3 weeks. Worth ~8.3 clicks/wk at share parity with the stage before. Source: SP-API SQP (sqp

    Tracked: on the task board at https://app.clickup.com/t/z8y71wzwx0 · finding sqp-funnel-cc-lao-gan-ma-spicy-chili-crisp-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-lao-gan-ma-spicy-chili-crisp-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-lao-gan-ma-spicy-chili-crisp-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-lao-gan-ma-spicy-chili-crisp-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  9. 250 visits a month raised yesterday

    ME — catalog details, images and settings are mine — the four things customers read are not

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 250 visits a month — that is not dollars.

    the evidence behind it
    [CLICK] "chili crisp" wk ending 2026-10-24: impr share 1.8% -> click share 0.9% -> cart 0.7% -> purchase share 0.9% (market 2016 purchases/wk, ours 18; 8 ASIN(s) pulled). Failing 3 of the last 3 weeks. Worth ~57.7 clicks/wk at share parity with the stage before. Source: SP-API SQP (sqp_funnel_gap.mj

    Tracked: on the task board at https://app.clickup.com/t/z8y71wzwwz · finding sqp-funnel-cc-chili-crisp-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crisp-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crisp-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crisp-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  10. 59 visits a month raised yesterday

    ME — catalog details, images and settings are mine — the four things customers read are not

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 59 visits a month — that is not dollars.

    the evidence behind it
    [CLICK] "chili crunch oil" wk ending 2026-10-24: impr share 6.0% -> click share 1.1% -> cart 1.3% -> purchase share 1.9% (market 53 purchases/wk, ours 1; 4 ASIN(s) pulled). Failing 3 of the last 3 weeks. Worth ~13.7 clicks/wk at share parity with the stage before. Source: SP-API SQP (sqp_funnel_gap.

    Tracked: on the task board at https://app.clickup.com/t/86eyxq1vz · finding sqp-funnel-cc-chili-crunch-oil-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crunch-oil-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crunch-oil-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crunch-oil-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  11. 78 visits a month raised yesterday

    ME — catalog details, images and settings are mine — the four things customers read are not

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 78 visits a month — that is not dollars.

    the evidence behind it
    [CLICK] "chilli crunch" wk ending 2026-10-24: impr share 9.3% -> click share 1.3% -> cart 1.3% -> purchase share 2.9% (market 70 purchases/wk, ours 2; 6 ASIN(s) pulled). Failing 3 of the last 3 weeks. Worth ~17.9 clicks/wk at share parity with the stage before. Source: SP-API SQP (sqp_funnel_gap.mjs

    Tracked: on the task board at https://app.clickup.com/t/86eyxq1v1 · finding sqp-funnel-cc-chilli-crunch-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chilli-crunch-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chilli-crunch-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chilli-crunch-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  12. 24 visits a month raised 9 days ago

    ME — catalog details, images and settings are mine — the four things customers read are not

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 24 visits a month — that is not dollars.

    the evidence behind it
    [CLICK] "chilli crisp" wk ending 2026-10-17: impr share 1.8% -> click share 1.0% -> cart 1.3% -> purchase share 1.8% (market 171 purchases/wk, ours 3; 2 ASIN(s) pulled). Failing 2 of the last 2 weeks. Worth ~5.6 clicks/wk at share parity with the stage before. Source: SP-API SQP (sqp_funnel_gap.mjs)

    Tracked: on the task board at https://app.clickup.com/t/z8y71wypan · finding sqp-funnel-cc-chilli-crisp-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chilli-crisp-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chilli-crisp-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chilli-crisp-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  13. 592 visits a month raised yesterday

    ME — catalog details, images and settings are mine — the four things customers read are not

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 592 visits a month — that is not dollars.

    the evidence behind it
    [CLICK] "chili crunch" wk ending 2026-10-24: impr share 10.5% -> click share 3.1% -> cart 2.2% -> purchase share 2.9% (market 557 purchases/wk, ours 16; 12 ASIN(s) pulled). Failing 2 of the last 3 weeks. Worth ~136.8 clicks/wk at share parity with the stage before. Source: SP-API SQP (sqp_funnel_gap

    Tracked: on the task board at https://app.clickup.com/t/86eyxq1ue · finding sqp-funnel-cc-chili-crunch-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crunch-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crunch-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crunch-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  14. not sized raised 15 days ago

    ME — changing bids, budgets and campaigns is already signed off — I fire one, re-read it live, then do the rest

    run the competitor-identification pass on this keyword, name who took the share, and attach it to this finding before the monthly strategy review decides the bid. CC chili crisp click_share 0.86%->0.53%, purchase_share 0.64%->0.45% (reversal).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Action: run the competitor-identification pass on this keyword, name who took the share, and attach it to this finding before the monthly strategy review decides the bid. CC chili crisp click_share 0.86%->0.53%, purchase_share 0.64%->0.45% (reversal).

    Tracked: on the task board at https://app.clickup.com/t/z8y71x13ff · finding cc-share-chili-crisp-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-share-chili-crisp-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-share-chili-crisp-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-share-chili-crisp-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  15. not sized raised 15 days ago

    ME — changing bids, budgets and campaigns is already signed off — I fire one, re-read it live, then do the rest

    run the competitor-identification pass on this keyword, name who took the share, and attach it to this finding before the monthly strategy review decides the bid. CC chili crunch purchase_share 1.36%->0.77% (reversal).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Action: run the competitor-identification pass on this keyword, name who took the share, and attach it to this finding before the monthly strategy review decides the bid. CC chili crunch purchase_share 1.36%->0.77% (reversal).

    Tracked: on the task board at https://app.clickup.com/t/z8y71x13fe · finding cc-share-chili-crunch-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-share-chili-crunch-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-share-chili-crunch-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-share-chili-crunch-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  16. not sized raised 32 days ago

    ME — the hidden search terms are not the wording customers read, so they are mine

    mode-7-comp: our purchase_share on "chili crisp" reversed upward — verify driver, consider pressing (DEFEND→conquest ladder).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    [STRUCTURAL] RECOVERY on "chili crisp" purchase_share: 2026-07:1.18% → 2026-08:0.5% → 2026-09:0.62% -- 3-month slope-sign flip with a >10% relative move (market-share-tracker.mjs detectShifts). Action: mode-7-comp: our purchase_share on "chili crisp" reversed upward — verify driver, consider pressin

    Tracked: on the task board at https://app.clickup.com/t/86eyz20ph · finding ba-full-matrix-cc-chili-crisp-purchase-share-2026-09.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crisp-purchase-share-2026-09 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crisp-purchase-share-2026-09 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crisp-purchase-share-2026-09 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  17. not sized raised 26 days ago

    ME — the hidden search terms are not the wording customers read, so they are mine

    mode-7-comp: our impr_share on "chili crunch" reversed upward — verify driver, consider pressing (DEFEND→conquest ladder).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    [STRUCTURAL] RECOVERY on "chili crunch" impr_share: 2026-07:6.64% → 2026-08:6.5% → 2026-09:7.2% -- 3-month slope-sign flip with a >10% relative move (market-share-tracker.mjs detectShifts). Action: mode-7-comp: our impr_share on "chili crunch" reversed upward — verify driver, consider pressing (DEFE

    Tracked: on the task board at https://app.clickup.com/t/z8y71wytg5 · finding ba-full-matrix-cc-chili-crunch-impr-share-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crunch-impr-share-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crunch-impr-share-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crunch-impr-share-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  18. not sized raised 7 days ago

    ME — the hidden search terms are not the wording customers read, so they are mine

    mode-7-comp window check + mode7-strategy: our purchase_share on "chili crisp" broke trend downward — find who took it (TST top-3) before the monthly strategy pass.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    [STRUCTURAL] REVERSAL on "chili crisp" purchase_share: 2026-08:0.5% → 2026-09:0.64% → 2026-10:0.45% -- 3-month slope-sign flip with a >10% relative move (market-share-tracker.mjs detectShifts). Action: mode-7-comp window check + mode7-strategy: our purchase_share on "chili crisp" broke trend downwar

    Tracked: on the task board at https://app.clickup.com/t/z8y71wytg7 · finding ba-full-matrix-cc-chili-crisp-purchase-share-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crisp-purchase-share-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crisp-purchase-share-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crisp-purchase-share-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  19. not sized raised 5 days ago

    ME — the hidden search terms are not the wording customers read, so they are mine

    mode-7-comp window check + mode7-strategy: our purchase_share on "chili crunch" broke trend downward — find who took it (TST top-3) before the monthly strategy pass.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    [STRUCTURAL] REVERSAL on "chili crunch" purchase_share: 2026-08:1.32% → 2026-09:1.36% → 2026-10:1.1% -- 3-month slope-sign flip with a >10% relative move (market-share-tracker.mjs detectShifts). Action: mode-7-comp window check + mode7-strategy: our purchase_share on "chili crunch" broke trend downw

    Tracked: on the task board at https://app.clickup.com/t/z8y71wztrr · finding ba-full-matrix-cc-chili-crunch-purchase-share-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crunch-purchase-share-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crunch-purchase-share-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crunch-purchase-share-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  20. not sized raised 32 days ago

    ME — changing bids, budgets and campaigns is already signed off — I fire one, re-read it live, then do the rest

    Size a Sponsored Brands budget increase for CC on the campaigns that share SP shoppers through mode7-strategy and hand it over for spend sign-off.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    AMC 2026-08-27..2026-09-26: shoppers who saw SP and SB converted at 28.26x the SP-only rate (25187 vs 88964 reach)

    Tracked: on the task board at https://app.clickup.com/t/86eyyj06p · finding amc-sb-overlap-CC.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amc-sb-overlap-CC --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amc-sb-overlap-CC --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amc-sb-overlap-CC --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

Booked, queued or already started

  • booked to run on 4 Nov 2026 - Claude Inventory Ledger EOM. Booked is not done.
  • booked to run on 12 Nov 2026 - Claude Reprice Scan Biweekly. Booked is not done.
  • in the queue - Sellerboard fee breakdown 2026-09-23/24: inbound placement fee $137.35 + inbound transport $319.18; CC P&L 2026-08-28..09-27

What we run for them

What we do for themStateLast doneHow often
catalog + economics solveup to date31 Oct 2026, todayevery 10 days
PPC engine run + auditup to date31 Oct 2026, todayevery 10 days
replenishment planup to date26 Oct 2026, 5 days agoevery 35 days
monthly reportup to date12 Oct 2026, 19 days agoevery 35 days
compliance / claims sweepup to date10 Oct 2026, 20 days agoevery 35 days

Goals

Sales goal

PeriodTargetSo farHow we are doingWho is working on itOpen item
This month 2026-10 $9,730 $7,338 as of Oct 25 Ahead (113% of pace) - goal-cc-mm1-net-2-000-mo-restore-hold-june-peak-2026-10-ladder
This quarter 2026-Q4 $32,170 $7,338 as of Oct 25 Ahead (113% of pace) - none open
This year 2026 $123,274 $97,245 as of Oct 25 Ahead (108% of pace) - goal-cc-mm1-net-2-000-mo-restore-hold-june-peak-2026-10-ladder

Next year (2027): $131,158 - proposed, not graded.

Last change made for this goal: 22 days ago.

The numbers

$1,742Kept after everythinggoal $2,000 a month
$258Short of the goalthis is what the work below is for
$9,072Soldin the last 30 days
14.6%Ad cost per sales dollarbreak-even is 37.8%, worked out on Aug 3
$1,025Open work wortha month, if we work it
What we measureWhere it is nowWhere it needs to beWhat that means
Sales$9,072in the last 30 dayseverything customers paid, before any costs come out
People who looked2,699no target sethow many visits the products got
How many of them bought10.4%no target setabout 1 in 10 of the people who look at it buys
Average order$32no target setwhat a customer spends when they do buy
Units sold281no target sethow many items went out of the door
Ad spend$1,327room for $2,102 morewhat we paid Amazon to put the products in front of people
Ad cost per sales dollar14.6%must stay under 37.8%under the line where ads stop paying for themselves. That line was worked out on Aug 3, and nothing re-checks it at the moment we change something
Kept per sales dollar33.8%no target setwhat is left of each dollar after Amazon, the product itself and the ads
Kept in total$1,742goal $2,000 a monththe number every piece of work below is trying to move

Measured as at 29 Oct 2026 (yesterday). Costs are known for 99% of the products, so what is kept is an upper bound, not a final figure. How the goal was set: DERIVED - M1 sized from June peak (net $2,009); tacos_ceiling = BE-ACoS 37.8% (workbook, COGS present). Flag for operator amendment

This board shows whether the numbers moved. It does not say we moved them - what our own work is measured to have earned is the separate figure further down.

The goal we are working to

Right now: push for growth - it earns more than it spends, so buy more of it - the account is growing.

Keep $2,000 a month, with ads staying under 37.8% of sales.

  1. M0 true landed break-evenACHIEVED - all 3 months positive already reached
  2. M1 net >= $2,000/mo (restore+hold June peak)June 2026 actual $2,009; July dipped to $1,527 - reachable in 1-2 cycles this is the one we are working to

Done this week

Since Oct 24: 3 things delivered, 0 findings acted on, 7 tickets closed, 0 automated runs.

Delivered to Downloads 3

  • 31 Oct 2026CC re check this ASIN on tomorrow s mode 7 comp run and rou
  • 27 Oct 2026CC run deal cover gate and the margin gate at event fees fo
  • 25 Oct 2026LMS Weekly

Findings acted on

No finding moved from open to fired, verified or measured since Oct 24.

Tickets closed 7

Automated runs

No scheduled job left a receipt for them since Oct 24.

What we have produced lately

  • 31 Oct 20262026-10-31__CC_re-check_this_ASIN_on_tomorrow_s_mode-7-comp_run_and_rou.pdf
  • 31 Oct 20262026-10-31__CC_re-check_this_ASIN_on_tomorrow_s_mode-7-comp_run_and_rou.html
  • 27 Oct 20262026-10-27__CC_run_deal_cover_gate_and_the_margin_gate_at_event_fees_fo.pdf
  • 27 Oct 20262026-10-27__CC_run_deal_cover_gate_and_the_margin_gate_at_event_fees_fo.html
  • 25 Oct 2026CC_LMS_Weekly_2026-10-25.pdf
  • 25 Oct 2026CC_LMS_Weekly_2026-10-25.html
  • 24 Oct 20262026-10-24__CC_I_need_you_to_give_me_Approve_or_decline_the_Chile_Crunc.pdf
  • 24 Oct 20262026-10-24__CC_I_need_you_to_give_me_Approve_or_decline_the_Chile_Crunc.html
  • 22 Oct 2026ChileColonial_InventoryLedger_SummaryMonthly_2026-09.csv
  • 21 Oct 20262026-10-21__CC_Find_out_why_B0CHBH22WD_converts_at_4_6_vs_the_catalog_s.pdf
  • 21 Oct 20262026-10-21__CC_Find_out_why_B0CHBH22WD_converts_at_4_6_vs_the_catalog_s.html
  • 21 Oct 20262026-10-21__CC_do_not_reprice_from_this_watch_route_to_the_operator_s_p.pdf

37 things produced for them in the last 30 days.

Did it work

Nothing of theirs has been scored yet. The first change counted in money finishes its waiting period on Nov 3: a tune-up of the ads, made Oct 20 (nobody has sized this yet).

1 change is inside the waiting period and will be scored when it ends. 20 went out without anyone writing down the before-figure, so they can never be scored - not late, unmeasurable.

What needs you — 23

  1. $78 a month raised 6 days ago

    YOU — choose remove, liquidate or discount for 110 aged Original 1-packs

    I need you to give me choose remove, liquidate or discount for 110 aged Original 1-packs. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on choose remove, liquidate or discount for 110 aged Original 1-packs — a number that exists only where you can get it, so no run of any job here will fill it in. This one is worth $78 a month.

    the evidence behind it
    LMS CC 2026-10-16: 110 Original 1-packs no sales, ~$78/mo aged fees; no decision as of 2026-10-25

    Tracked: NOT on the task board — nothing is chasing it but this row · finding lms-CC-aged-1pack-storage.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-aged-1pack-storage --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-aged-1pack-storage --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-aged-1pack-storage --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  2. 887 visits a month raised 2 days ago

    YOU — the selling price is one of the four things I never change without you

    Match or beat the $14.99 Buy Box price on B07R7XDXHH (SKU 003) in Seller Central Automate Pricing (operator's click, minimum is $19.00 today), then re-read the live offer to confirm the Buy Box returned.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 887 visits a month — that is not dollars.

    the evidence behind it
    2026-10-29 live SP-API offers: our SKU 003 on B07R7XDXHH is listed at $19.00, Buy Box winner is another seller at $14.99 (8 offers); Business Report Buy Box share 0.2% on 887 sessions, 0 units. Gap $4.01 is past the ~$3.00 re-open condition on the 09-02 hold (cc-chili-crisp-price-floor-held-at-19-by

    Tracked: on the task board at https://app.clickup.com/t/z8y71x0yrp · finding reprice-scan-CC-B07R7XDXHH-buybox.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id reprice-scan-CC-B07R7XDXHH-buybox --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id reprice-scan-CC-B07R7XDXHH-buybox --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id reprice-scan-CC-B07R7XDXHH-buybox --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  3. not sized raised 4 days ago

    YOU — the selling price is one of the four things I never change without you

    open the promo Issues tab on the Chile Colonial account, decode the error, and stage the fix for operator sign-off before 2026-11-13.

    There is a dated opportunity on this account - a deal, a promotion or a shopping event - and the window to use it closes. Missing it is not a mistake we can fix afterwards. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Live Promotion Central read 2026-10-27: CC BFCM Prime 20pct deal products (PriceDiscount, 11/19-11/30, 4 ASINs) is SUPPRESSED with 1 error and an empty benefit; sourcing closes 2026-11-13; fee 100 USD one-time + 1.5% performance; unsized, no measured lift. Action: open the promo Issues tab on the Ch

    Tracked: on the task board at https://app.clickup.com/t/z8y71x3f80 · finding amazon-promotions-CC-bfcm-prime-20pct-suppressed.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-CC-bfcm-prime-20pct-suppressed --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-CC-bfcm-prime-20pct-suppressed --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-CC-bfcm-prime-20pct-suppressed --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

the other 20 waiting on you, in the same order
  1. not sized raised 4 days ago

    YOU — the selling price is one of the four things I never change without you

    run deal_cover_gate and the margin gate at event fees for B07R7XDXHH, then stage the nomination for operator sign-off before 2026-11-13.

    There is a dated opportunity on this account - a deal, a promotion or a shopping event - and the window to use it closes. Missing it is not a mistake we can fix afterwards. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Deals dashboard 2026-10-27: Amazon recommends Best Deal and Lightning Deal for B07R7XDXHH + 14 variations in Black Friday/Cyber Monday; submit-by 2026-11-13; deal fees apply so never auto-nominated; unsized. Action: run deal_cover_gate and the margin gate at event fees for B07R7XDXHH, then stage the

    Tracked: on the task board at https://app.clickup.com/t/z8y71x3f81 · finding amazon-promotions-CC-bfcm-deal-recommendation.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-CC-bfcm-deal-recommendation --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-CC-bfcm-deal-recommendation --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-CC-bfcm-deal-recommendation --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  2. not sized raised 7 days ago

    YOU — Approve or decline the Chile Crunch BFCM Best Deal and Lightning Deal recommendations (nominations close Nov 13); tentpole deals are never auto-nominated

    I need you to give me Approve or decline the Chile Crunch BFCM Best Deal and Lightning Deal recommendations (nominations close Nov 13); tentpole deals are never auto-nominated. I cannot get this anywhere else — re-running /amazon-promotions CC would only raise the same finding again, so nothing moves until you send it. Once you have, I run /amazon-promotions CC and work it to a decision.

    This one is stuck waiting on Approve or decline the Chile Crunch BFCM Best Deal and Lightning Deal recommendations (nominations close Nov 13); tentpole deals are never auto-nominated — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    CC deals dashboard shows BFCM Best Deal and Lightning Deal recommendations open until Nov 13, 2026 (20 days). Deals carry fees and are invite-only per ASIN. Action: decide per-ASIN deal price against landed margin and nominate or decline before Nov 13.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x30xm · finding amazon-promotions-cc-bfcm-deals-nomination.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-cc-bfcm-deals-nomination --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-cc-bfcm-deals-nomination --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-cc-bfcm-deals-nomination --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  3. $448 a month raised 6 days ago

    YOU — approve shipping 46 x 31oz party jars (SKU 031 fba) by 31 Oct

    I need you to give me approve shipping 46 x 31oz party jars (SKU 031 fba) by 31 Oct. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on approve shipping 46 x 31oz party jars (SKU 031 fba) by 31 Oct — a number that exists only where you can get it, so no run of any job here will fill it in. This one is worth $448 a month.

    the evidence behind it
    Sellerboard inventory 2026-10-25: 031 fba FBA 0 sellable, 24 fc_transfer, vel 0.94/d, price 46.99, Amazon rec 46 by 2026-10-31; delta = 0.94*46.99*30*0.338243

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyu3r · finding lms-CC-party-jar-shipin-2026-10-05.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-party-jar-shipin-2026-10-05 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-party-jar-shipin-2026-10-05 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-party-jar-shipin-2026-10-05 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  4. not sized raised 15 days ago

    YOU — Approve retiring the dead duplicate SKU Orig-2-FBA (0 stock, false 464-unit restock prompt)

    I need you to give me Approve retiring the dead duplicate SKU Orig-2-FBA (0 stock, false 464-unit restock prompt). I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on Approve retiring the dead duplicate SKU Orig-2-FBA (0 stock, false 464-unit restock prompt) — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Sellerboard 2026-10-16: Orig-2-FBA 0 units, Recommended_ship_in_quantity 464; live twin 004-FBA 333 avail +142 inbound, 75 days

    Tracked: on the task board at https://app.clickup.com/t/86eyxa2zp · finding lms-CC-dead-duplicate-sku-orig-2-fba.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-dead-duplicate-sku-orig-2-fba --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-dead-duplicate-sku-orig-2-fba --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-dead-duplicate-sku-orig-2-fba --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  5. not sized raised 6 days ago

    YOU — yes/no on BFCM Best Deal and Lightning Deal nominations

    I need you to give me yes/no on BFCM Best Deal and Lightning Deal nominations. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on yes/no on BFCM Best Deal and Lightning Deal nominations — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    operator digest 2026-10-24 + lever amazon-promotions-cc-bfcm-deals-nomination OPEN 2026-10-25

    Tracked: on the task board at https://app.clickup.com/t/z8y71x13j0 · finding lms-CC-bfcm-deal-submit-by-1020.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-bfcm-deal-submit-by-1020 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-bfcm-deal-submit-by-1020 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-bfcm-deal-submit-by-1020 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  6. not sized raised 4 days ago

    YOU — the unit cost (ex-shipping) for CC B07QSSCQ9S

    I need you to give me the unit cost (ex-shipping) for CC B07QSSCQ9S. I cannot get this anywhere else — re-running /goal-cascade CC would only raise the same finding again, so nothing moves until you send it. Once you have, I run /goal-cascade CC and work it to a decision.

    This one is stuck waiting on the unit cost (ex-shipping) for CC B07QSSCQ9S — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    CC readiness cogs: 1 selling ASIN(s) with a $0 cost: B07QSSCQ9S - profit is UNSIZED for these (newest cost source 58 day(s) old (STALE, over 21 days)) (source: Sync/cogs/CC.json; projects/mode6-catalog-gap-audit/inputs_CC/CC_Sellerboard_economics.json; projects/mode6-catalog-gap-audit/inputs_CC/CC_B

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyx7j · finding goal-cc-readiness-cogs.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id goal-cc-readiness-cogs --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id goal-cc-readiness-cogs --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id goal-cc-readiness-cogs --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  7. not sized raised today

    YOU — the selling price is one of the four things I never change without you

    re-check this ASIN on tomorrow's mode-7-comp run and route it to the monthly strategy review once the window's close date is known. Signals 2026-10-31: competitor B0CHC8J7DR (Spice World) raised price to $22.99 (live SP-API matches; 39.8% above previous live read 2026-10-25 (read 2026-10-31); opened 2026-10-26) vs our…

    There is a dated opportunity on this account - a deal, a promotion or a shopping event - and the window to use it closes. Missing it is not a mistake we can fix afterwards. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Action: re-check this ASIN on tomorrow's mode-7-comp run and route it to the monthly strategy review once the window's close date is known. Signals 2026-10-31: competitor B0CHC8J7DR (Spice World) raised price to $22.99 (live SP-API matches; 39.8% above previous live read 2026-10-25 (read 2026-10-31)

    Tracked: on the task board at https://app.clickup.com/t/z8y71x363j · finding mktwatch-CC-B012TZUT7W-comp-windows.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B012TZUT7W-comp-windows --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B012TZUT7W-comp-windows --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B012TZUT7W-comp-windows --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  8. not sized raised today

    YOU — the selling price is one of the four things I never change without you

    re-check this ASIN on tomorrow's mode-7-comp run and route it to the monthly strategy review once the window's close date is known. Signals 2026-10-31: competitor B0FGTK2WXY (STARTZYK) raised price to $26.99 (live SP-API matches; 12.5% above previous live read 2026-10-30; opened 2026-10-31) vs our B08KH7J9XS. Likely…

    There is a dated opportunity on this account - a deal, a promotion or a shopping event - and the window to use it closes. Missing it is not a mistake we can fix afterwards. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Action: re-check this ASIN on tomorrow's mode-7-comp run and route it to the monthly strategy review once the window's close date is known. Signals 2026-10-31: competitor B0FGTK2WXY (STARTZYK) raised price to $26.99 (live SP-API matches; 12.5% above previous live read 2026-10-30; opened 2026-10-31)

    Tracked: on the task board at https://app.clickup.com/t/z8y71wya7b · finding mktwatch-CC-B0CH8CLVZJ-comp-pricerise.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B0CH8CLVZJ-comp-pricerise --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B0CH8CLVZJ-comp-pricerise --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B0CH8CLVZJ-comp-pricerise --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  9. $327 a month raised 3 days ago

    YOU — the wording customers read — the title, the bullet points or the description

    Find out why B0CHBH22WD converts at 4.6% vs the catalog's 13.2%: check it is buyable and in stock, its images, rating and reviews, and its price against sibling products. If the listing is the cause, prepare a MODE4/MODE5 draft for approval (no live edit); otherwise drop the finding with the evidence.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. This one is worth $327 a month.

    the evidence behind it
    [KPI M1 net >= $2,000/mo (restore+hold June peak) | cm_dollars_monthly>=2000 | posture scale-up] MODE 6 engine, source report BusinessReport: B0CHBH22WD Unit Session % = 4.60% -> $327/mo at stake (CONFIRMED). Action: Find out why B0CHBH22WD converts at 4.6% vs the catalog's 13.2%: check it is buyabl

    Tracked: on the task board at https://app.clickup.com/t/z8y71x20pg · finding mode6-cc-conversion-b0chbh22wd.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode6-cc-conversion-b0chbh22wd --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode6-cc-conversion-b0chbh22wd --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode6-cc-conversion-b0chbh22wd --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  10. $115 a month raised 3 days ago

    YOU — the wording customers read — the title, the bullet points or the description

    Find out why B07QSSCQ9S converts at 2.9% vs the catalog's 13.2%: check it is buyable and in stock, its images, rating and reviews, and its price against sibling products. If the listing is the cause, prepare a MODE4/MODE5 draft for approval (no live edit); otherwise drop the finding with the evidence.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. This one is worth $115 a month.

    the evidence behind it
    [KPI M1 net >= $2,000/mo (restore+hold June peak) | cm_dollars_monthly>=2000 | posture scale-up] MODE 6 engine, source report BusinessReport: B07QSSCQ9S Unit Session % = 2.94% -> $115/mo at stake (CONFIRMED). Action: Find out why B07QSSCQ9S converts at 2.9% vs the catalog's 13.2%: check it is buyabl

    Tracked: NOT on the task board — nothing is chasing it but this row · finding mode6-cc-conversion-b07qsscq9s.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode6-cc-conversion-b07qsscq9s --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode6-cc-conversion-b07qsscq9s --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode6-cc-conversion-b07qsscq9s --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  11. not sized raised 20 days ago

    YOU — the wording customers read — the title, the bullet points or the description

    Run mode4 on CC to cut the titles of B012TZUT7W, B08KH7J9XS, B01MF7XAU3, B07R7XDXHH, B0CK89MPGJ, B0BNW6X82G, B0CHBHFVDX to 200 chars or fewer.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Action: Run mode4 on CC to cut the titles of B012TZUT7W, B08KH7J9XS, B01MF7XAU3, B07R7XDXHH, B0CK89MPGJ, B0BNW6X82G, B0CHBHFVDX to 200 chars or fewer. Re-measured 2026-10-10 SP-API listings pull: still NOT live on 14 SKUs (B08KH7J9XS 213 chars, the other six 201 chars) despite the lever reading FIRE

    Tracked: on the task board at https://app.clickup.com/t/86eym4um9 · finding claims-audit-CC-title-cap.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id claims-audit-CC-title-cap --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id claims-audit-CC-title-cap --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id claims-audit-CC-title-cap --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  12. not sized raised 6 days ago

    YOU — approve the prepared file of 14 shortened titles

    I need you to give me approve the prepared file of 14 shortened titles. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on approve the prepared file of 14 shortened titles — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    claims-audit CC 2026-10-10: 14 titles over 200 chars; still NOT-LIVE 2026-10-25

    Tracked: on the task board at https://app.clickup.com/t/z8y71x011w · finding lms-CC-title-cap-not-live.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-title-cap-not-live --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-title-cap-not-live --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-title-cap-not-live --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  13. 566 visits a month raised 14 days ago

    YOU — Approve or decline conquest spend on this rival-brand query: new product targets + an exact-match bid are growth spend, posture-gated by the client KPI contract; on a yes, MODE 7 builds it PAUSED, canaries one and enables last.

    I need you to give me Approve or decline conquest spend on this rival-brand query: new product targets + an exact-match bid are growth spend, posture-gated by the client KPI contract; on a yes, MODE 7 builds it PAUSED, canaries one and enables last.. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on Approve or decline conquest spend on this rival-brand query: new product targets + an exact-match bid are growth spend, posture-gated by the client KPI contract; on a yes, MODE 7 builds it PAUSED, canaries one and enables last. — a number that exists only where you can get it, so no run of any job here will fill it in. This one is sized at 566 visits a month — that is not dollars.

    the evidence behind it
    [CONQUEST rival=MOMOFUKU B09DS5J8F9/B0FQFKZQB5/B09TX2GD4J] "momofuku chili crunch" wk ending 2026-09-26: impr share 7.0% -> click share 0.3% -> cart 0.0% -> purchase share 0.0% (market 589 purchases/wk, ours 0; 7 ASIN(s) pulled). Failing 3 of the last 3 weeks. Worth ~130.8 clicks/wk at share parity

    Tracked: on the task board at https://app.clickup.com/t/86eyxq1tq · finding sqp-funnel-cc-momofuku-chili-crunch-conquest.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-momofuku-chili-crunch-conquest --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-momofuku-chili-crunch-conquest --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-momofuku-chili-crunch-conquest --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  14. not sized raised 4 days ago

    YOU — the selling price is one of the four things I never change without you

    prepare a non-price listing fix for the 'manufacturer' attribute conflict on SKU 003-FBA (Merchant 'Chile Colonial LLC' vs catalog 'Chile Crunch') and hand it to the operator to approve; do NOT reprice. B07R7XDXHH is NOT ELIGIBLE to be the Featured Offer (Seller Central Pricing Health 2026-10-27, flagged 2026-10-22…

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Action: prepare a non-price listing fix for the 'manufacturer' attribute conflict on SKU 003-FBA (Merchant 'Chile Colonial LLC' vs catalog 'Chile Crunch') and hand it to the operator to approve; do NOT reprice. B07R7XDXHH is NOT ELIGIBLE to be the Featured Offer (Seller Central Pricing Health 2026-1

    Tracked: on the task board at https://app.clickup.com/t/z8y71x0637 · finding mktwatch-CC-B07R7XDXHH-featured-offer-price-gate.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B07R7XDXHH-featured-offer-price-gate --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B07R7XDXHH-featured-offer-price-gate --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B07R7XDXHH-featured-offer-price-gate --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  15. not sized raised 15 days ago

    YOU — Approve the prepared file CC-title-overcap-fixes-2026-10-11.html

    I need you to give me Approve the prepared file CC-title-overcap-fixes-2026-10-11.html. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on Approve the prepared file CC-title-overcap-fixes-2026-10-11.html — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    claims-audit/CC/2026-10-10/flags.csv 14 BLOCK / 30 WARN; scorecard compliance F 2026-10-16

    Tracked: on the task board at https://app.clickup.com/t/86eywfbx9 · finding lms-CC-compliance-warn-backlog.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-compliance-warn-backlog --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-compliance-warn-backlog --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-compliance-warn-backlog --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  16. not sized raised 4 days ago

    YOU — the wording customers read — the title, the bullet points or the description

    prepare a mode4 title + description DRAFT for CC for operator approval (LMS: title/bullets/description always need him); no live edit, no price change.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    CC readiness copy: coverage audit: title N, description N (source: readiness_map.json coverage_audit (an audit read, not a live measurement))

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyx61 · finding goal-cc-readiness-copy.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id goal-cc-readiness-copy --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id goal-cc-readiness-copy --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id goal-cc-readiness-copy --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  17. 139 visits a month raised 14 days ago

    YOU — Approve or decline an exact-match bid RAISE on this query in a Tab_07 workbook: a raise is never fired unattended; on a yes, /mode7-run applies the approved Tab_07 row (posture-capped).

    I need you to give me Approve or decline an exact-match bid RAISE on this query in a Tab_07 workbook: a raise is never fired unattended; on a yes, /mode7-run applies the approved Tab_07 row (posture-capped).. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on Approve or decline an exact-match bid RAISE on this query in a Tab_07 workbook: a raise is never fired unattended; on a yes, /mode7-run applies the approved Tab_07 row (posture-capped). — a number that exists only where you can get it, so no run of any job here will fill it in. This one is sized at 139 visits a month — that is not dollars.

    the evidence behind it
    [IMPRESSION] "garlic chili oil" wk ending 2026-10-10: impr share 0.0% -> click share 0.3% -> cart 0.5% -> purchase share 1.3% (market 78 purchases/wk, ours 1; 1 ASIN(s) pulled). Failing 1 of the last 1 weeks. Worth ~32.1 clicks/wk per +1 point of impression share. Source: SP-API SQP (sqp_funnel_gap.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x1299 · finding sqp-funnel-cc-garlic-chili-oil-impression.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-garlic-chili-oil-impression --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-garlic-chili-oil-impression --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-garlic-chili-oil-impression --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  18. not sized raised 4 days ago

    YOU — approve the mode4 title + description draft before it is published

    I need you to give me approve the mode4 title + description draft before it is published. I cannot get this anywhere else — re-running /mode4 CC would only raise the same finding again, so nothing moves until you send it. Once you have, I run /mode4 CC and work it to a decision.

    This one is stuck waiting on approve the mode4 title + description draft before it is published — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    [KPI M1 net >= $2,000/mo (restore+hold June peak) | cm_dollars_monthly>=2000 | posture scale-up] readiness gap "copy": coverage audit: title N, description N (goal_history/readiness/CC.json)

    Tracked: on the task board at https://app.clickup.com/t/z8y71x18dm · finding mode4-cc-copy-readiness.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode4-cc-copy-readiness --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode4-cc-copy-readiness --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode4-cc-copy-readiness --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  19. not sized raised 58 days ago

    YOU — the wording customers read — the title, the bullet points or the description

    Run mode5-update on the main image and check price + rating count for "chili crisp" — shoppers see us on this query and click a competitor.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    SQP share shape CARD-LOSES-CLICK on "chili crisp" — we win a smaller slice of the clicks than of the impressions (2026-08: impressions 0.59x reference), held in 3 of 3 months read; source ~/mode7-analysis/market_share_CC_2026-09.json

    Tracked: on the task board at https://app.clickup.com/t/86eyu6j79 · finding share-shape-CC-chili-crisp.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-shape-CC-chili-crisp --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-shape-CC-chili-crisp --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-shape-CC-chili-crisp --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  20. not sized raised 58 days ago

    YOU — the wording customers read — the title, the bullet points or the description

    Run mode5-update on the main image and check price + rating count for "chili crunch" — shoppers see us on this query and click a competitor.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    SQP share shape CARD-LOSES-CLICK on "chili crunch" — we win a smaller slice of the clicks than of the impressions (2026-08: impressions 0.31x reference), held in 3 of 3 months read; source ~/mode7-analysis/market_share_CC_2026-09.json

    Tracked: on the task board at https://app.clickup.com/t/86eyu6j78 · finding share-shape-CC-chili-crunch.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-shape-CC-chili-crunch --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-shape-CC-chili-crunch --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-shape-CC-chili-crunch --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

Their task board — 8 of them past due

Ranked by what each one is worth to the account per month, highest first. 3 of the 50 carry a dollar figure, $813 a month between them. 8 are tickets with no finding behind them at all, so they appear on no other tab on this page.

  1. $448 a month

    I need you to give me approve shipping 46 x 31oz party jars (SKU 031 fba) by 31 Oct. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on approve shipping 46 x 31oz party jars (SKU 031 fba) by 31 Oct — a number that exists only where you can get it, so no run of any job here will fill it in. This one is worth $448 a month.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyu3r · finding lms-CC-party-jar-shipin-2026-10-05.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-party-jar-shipin-2026-10-05 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-party-jar-shipin-2026-10-05 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-party-jar-shipin-2026-10-05 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  2. $327 a month

    Find out why B0CHBH22WD converts at 4.6% vs the catalog's 13.2%: check it is buyable and in stock, its images, rating and reviews, and its price against sibling products. If the listing is the cause, prepare a MODE4/MODE5 draft for approval (no live edit); otherwise drop the finding with the evidence.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. This one is worth $327 a month.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x20pg · finding mode6-cc-conversion-b0chbh22wd.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode6-cc-conversion-b0chbh22wd --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode6-cc-conversion-b0chbh22wd --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode6-cc-conversion-b0chbh22wd --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  3. $37 a month

    Open the FBA reimbursement case for CC in Seller Central for 2 Lost units (004-FBA B012TZUT7W 1, 013 fba B08KHPTBVL 1) and 3 net Unknown-Event units (Hot-2-FBA B0CHBH22WD 2, Variety-4-FBA B0CHBDMCHS 1) before the claim window closes.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. It is usually spend that produced nothing, a fee charged wrongly, or stock Amazon owes for. This one is worth $37 a month.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x0hfq · finding ledgereom-CC-2026-09-lost-unreconciled.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ledgereom-CC-2026-09-lost-unreconciled --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ledgereom-CC-2026-09-lost-unreconciled --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ledgereom-CC-2026-09-lost-unreconciled --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  4. 45 visits a month

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 45 visits a month — that is not dollars.

    Tracked: on the task board at https://app.clickup.com/t/86eyxq1w4 · finding sqp-funnel-cc-chili-onion-crunch-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-onion-crunch-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-onion-crunch-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-onion-crunch-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  5. not sized

    Verify what drove the purchase-share recovery on "chili crisp" and consider pressing via the conquest ladder before the monthly strategy review.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wxw7y · finding cc-chili-crisp-purchase-share-2026-09.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-chili-crisp-purchase-share-2026-09 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-chili-crisp-purchase-share-2026-09 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-chili-crisp-purchase-share-2026-09 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  6. 36 visits a month

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 36 visits a month — that is not dollars.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wzwx0 · finding sqp-funnel-cc-lao-gan-ma-spicy-chili-crisp-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-lao-gan-ma-spicy-chili-crisp-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-lao-gan-ma-spicy-chili-crisp-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-lao-gan-ma-spicy-chili-crisp-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  7. not sized

    Run mode4 on CC to cut the titles of B012TZUT7W, B08KH7J9XS, B01MF7XAU3, B07R7XDXHH, B0CK89MPGJ, B0BNW6X82G, B0CHBHFVDX to 200 chars or fewer.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/86eym4um9 · finding claims-audit-CC-title-cap.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id claims-audit-CC-title-cap --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id claims-audit-CC-title-cap --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id claims-audit-CC-title-cap --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  8. not sized

    run the competitor-identification pass on this keyword, name who took the share, and attach it to this finding before the monthly strategy review decides the bid. CC chili crisp click_share 0.86%->0.53%, purchase_share 0.64%->0.45% (reversal).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x13ff · finding cc-share-chili-crisp-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-share-chili-crisp-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-share-chili-crisp-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-share-chili-crisp-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  9. not sized

    run the competitor-identification pass on this keyword, name who took the share, and attach it to this finding before the monthly strategy review decides the bid. CC chili crunch purchase_share 1.36%->0.77% (reversal).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x13fe · finding cc-share-chili-crunch-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-share-chili-crunch-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-share-chili-crunch-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id cc-share-chili-crunch-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  10. not sized

    I need you to give me Approve the prepared file CC-title-overcap-fixes-2026-10-11.html. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on Approve the prepared file CC-title-overcap-fixes-2026-10-11.html — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/86eywfbx9 · finding lms-CC-compliance-warn-backlog.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-compliance-warn-backlog --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-compliance-warn-backlog --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-compliance-warn-backlog --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  11. 139 visits a month

    I need you to give me Approve or decline an exact-match bid RAISE on this query in a Tab_07 workbook: a raise is never fired unattended; on a yes, /mode7-run applies the approved Tab_07 row (posture-capped).. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on Approve or decline an exact-match bid RAISE on this query in a Tab_07 workbook: a raise is never fired unattended; on a yes, /mode7-run applies the approved Tab_07 row (posture-capped). — a number that exists only where you can get it, so no run of any job here will fill it in. This one is sized at 139 visits a month — that is not dollars.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x1299 · finding sqp-funnel-cc-garlic-chili-oil-impression.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-garlic-chili-oil-impression --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-garlic-chili-oil-impression --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-garlic-chili-oil-impression --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  12. 566 visits a month

    I need you to give me Approve or decline conquest spend on this rival-brand query: new product targets + an exact-match bid are growth spend, posture-gated by the client KPI contract; on a yes, MODE 7 builds it PAUSED, canaries one and enables last.. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on Approve or decline conquest spend on this rival-brand query: new product targets + an exact-match bid are growth spend, posture-gated by the client KPI contract; on a yes, MODE 7 builds it PAUSED, canaries one and enables last. — a number that exists only where you can get it, so no run of any job here will fill it in. This one is sized at 566 visits a month — that is not dollars.

    Tracked: on the task board at https://app.clickup.com/t/86eyxq1tq · finding sqp-funnel-cc-momofuku-chili-crunch-conquest.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-momofuku-chili-crunch-conquest --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-momofuku-chili-crunch-conquest --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-momofuku-chili-crunch-conquest --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  13. 24 visits a month

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 24 visits a month — that is not dollars.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wypan · finding sqp-funnel-cc-chilli-crisp-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chilli-crisp-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chilli-crisp-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chilli-crisp-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  14. not sized

    run the competitor-identification pass on the CC share-shift keywords ("chili crunch" purchase_share 1.36%->0.77%, "chili crisp" click_share 0.86%->0.53%) listed in drift_findings_latest.md, name who took the share, and attach it to this finding before the monthly strategy review decides the bid. Unsized.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x32u0 · finding drift-mshare-cc-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id drift-mshare-cc-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id drift-mshare-cc-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id drift-mshare-cc-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  15. not sized

    Run /mode7-run on the next Monday cycle to read the 20 Oct cuts and restore exact-term traffic on chili crunch / chili crisp.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x32et · finding lms-CC-sessions-decline-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-sessions-decline-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-sessions-decline-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-sessions-decline-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  16. not sized

    I need you to give me approve the prepared file of 14 shortened titles. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on approve the prepared file of 14 shortened titles — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x011w · finding lms-CC-title-cap-not-live.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-title-cap-not-live --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-title-cap-not-live --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-title-cap-not-live --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  17. not sized

    run the competitor-identification pass on keywords 'chili crunch' and 'chili crisp', name who took the share, and attach it to this finding before the monthly strategy review decides the bid. Purchase share chili crunch 1.36% to 0.77%; chili crisp click share 0.86% to 0.53%, purchase share 0.64% to 0.45%.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x32ea · finding share-cc-chili-crisp-crunch-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-cc-chili-crisp-crunch-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-cc-chili-crisp-crunch-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-cc-chili-crisp-crunch-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  18. not sized

    prepare a non-price listing fix for the 'manufacturer' attribute conflict on SKU 003-FBA (Merchant 'Chile Colonial LLC' vs catalog 'Chile Crunch') and hand it to the operator to approve; do NOT reprice. B07R7XDXHH is NOT ELIGIBLE to be the Featured Offer (Seller Central Pricing Health 2026-10-27, flagged 2026-10-22…

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x0637 · finding mktwatch-CC-B07R7XDXHH-featured-offer-price-gate.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B07R7XDXHH-featured-offer-price-gate --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B07R7XDXHH-featured-offer-price-gate --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B07R7XDXHH-featured-offer-price-gate --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  19. 887 visits a month

    Match or beat the $14.99 Buy Box price on B07R7XDXHH (SKU 003) in Seller Central Automate Pricing (operator's click, minimum is $19.00 today), then re-read the live offer to confirm the Buy Box returned.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 887 visits a month — that is not dollars.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x0yrp · finding reprice-scan-CC-B07R7XDXHH-buybox.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id reprice-scan-CC-B07R7XDXHH-buybox --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id reprice-scan-CC-B07R7XDXHH-buybox --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id reprice-scan-CC-B07R7XDXHH-buybox --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  20. 250 visits a month

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 250 visits a month — that is not dollars.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wzwwz · finding sqp-funnel-cc-chili-crisp-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crisp-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crisp-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crisp-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  21. 592 visits a month

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 592 visits a month — that is not dollars.

    Tracked: on the task board at https://app.clickup.com/t/86eyxq1ue · finding sqp-funnel-cc-chili-crunch-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crunch-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crunch-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crunch-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  22. 59 visits a month

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 59 visits a month — that is not dollars.

    Tracked: on the task board at https://app.clickup.com/t/86eyxq1vz · finding sqp-funnel-cc-chili-crunch-oil-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crunch-oil-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crunch-oil-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chili-crunch-oil-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  23. 78 visits a month

    mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 78 visits a month — that is not dollars.

    Tracked: on the task board at https://app.clickup.com/t/86eyxq1v1 · finding sqp-funnel-cc-chilli-crunch-click.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chilli-crunch-click --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chilli-crunch-click --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id sqp-funnel-cc-chilli-crunch-click --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  24. not sized

    re-check this ASIN on tomorrow's mode-7-comp run and route it to the monthly strategy review once the window's close date is known. Signals 2026-10-31: competitor B0CHC8J7DR (Spice World) raised price to $22.99 (live SP-API matches; 39.8% above previous live read 2026-10-25 (read 2026-10-31); opened 2026-10-26) vs our…

    There is a dated opportunity on this account - a deal, a promotion or a shopping event - and the window to use it closes. Missing it is not a mistake we can fix afterwards. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x363j · finding mktwatch-CC-B012TZUT7W-comp-windows.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B012TZUT7W-comp-windows --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B012TZUT7W-comp-windows --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B012TZUT7W-comp-windows --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  25. not sized

    re-check this ASIN on tomorrow's mode-7-comp run and route it to the monthly strategy review once the window's close date is known. Signals 2026-10-31: competitor B0FGTK2WXY (STARTZYK) raised price to $26.99 (live SP-API matches; 12.5% above previous live read 2026-10-30; opened 2026-10-31) vs our B08KH7J9XS. Likely…

    There is a dated opportunity on this account - a deal, a promotion or a shopping event - and the window to use it closes. Missing it is not a mistake we can fix afterwards. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wya7b · finding mktwatch-CC-B0CH8CLVZJ-comp-pricerise.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B0CH8CLVZJ-comp-pricerise --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B0CH8CLVZJ-comp-pricerise --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mktwatch-CC-B0CH8CLVZJ-comp-pricerise --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  26. not sized

    On the next CC shipment run /send-to-amazon and choose Amazon-optimized splits to avoid the inbound placement fee.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. It is usually spend that produced nothing, a fee charged wrongly, or stock Amazon owes for. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wxw94 · finding lms-CC-inbound-placement-fee.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-inbound-placement-fee --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-inbound-placement-fee --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-inbound-placement-fee --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  27. not sized

    I need you to give me Approve retiring the dead duplicate SKU Orig-2-FBA (0 stock, false 464-unit restock prompt). I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on Approve retiring the dead duplicate SKU Orig-2-FBA (0 stock, false 464-unit restock prompt) — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/86eyxa2zp · finding lms-CC-dead-duplicate-sku-orig-2-fba.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-dead-duplicate-sku-orig-2-fba --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-dead-duplicate-sku-orig-2-fba --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-dead-duplicate-sku-orig-2-fba --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  28. not sized

    I need you to give me yes/no on BFCM Best Deal and Lightning Deal nominations. I cannot get this anywhere else — re-running the job that raised this would only raise the same finding again, so nothing moves until you send it.

    This one is stuck waiting on yes/no on BFCM Best Deal and Lightning Deal nominations — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x13j0 · finding lms-CC-bfcm-deal-submit-by-1020.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-bfcm-deal-submit-by-1020 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-bfcm-deal-submit-by-1020 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-bfcm-deal-submit-by-1020 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  29. not sized

    Run mode5-update on the main image and check price + rating count for "chili crisp" — shoppers see us on this query and click a competitor.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/86eyu6j79 · finding share-shape-CC-chili-crisp.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-shape-CC-chili-crisp --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-shape-CC-chili-crisp --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-shape-CC-chili-crisp --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  30. not sized

    Run mode5-update on the main image and check price + rating count for "chili crunch" — shoppers see us on this query and click a competitor.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/86eyu6j78 · finding share-shape-CC-chili-crunch.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-shape-CC-chili-crunch --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-shape-CC-chili-crunch --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id share-shape-CC-chili-crunch --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  31. not sized

    Size a Sponsored Brands budget increase for CC on the campaigns that share SP shoppers through mode7-strategy and hand it over for spend sign-off.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/86eyyj06p · finding amc-sb-overlap-CC.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amc-sb-overlap-CC --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amc-sb-overlap-CC --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amc-sb-overlap-CC --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  32. not sized

    mode-7-comp: our purchase_share on "chili crisp" reversed upward — verify driver, consider pressing (DEFEND→conquest ladder).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/86eyz20ph · finding ba-full-matrix-cc-chili-crisp-purchase-share-2026-09.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crisp-purchase-share-2026-09 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crisp-purchase-share-2026-09 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crisp-purchase-share-2026-09 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  33. not sized

    Search-term and placement audit on the Sep spend increase; cut non-converting terms back to Aug spend level.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyz14 · finding mom-CC-spend-up-sales-down-2026-09.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mom-CC-spend-up-sales-down-2026-09 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mom-CC-spend-up-sales-down-2026-09 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mom-CC-spend-up-sales-down-2026-09 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  34. not sized

    mode-7-comp: our impr_share on "chili crunch" reversed upward — verify driver, consider pressing (DEFEND→conquest ladder).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wytg5 · finding ba-full-matrix-cc-chili-crunch-impr-share-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crunch-impr-share-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crunch-impr-share-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crunch-impr-share-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  35. not sized

    I need you to give me Approve or decline the Chile Crunch BFCM Best Deal and Lightning Deal recommendations (nominations close Nov 13); tentpole deals are never auto-nominated. I cannot get this anywhere else — re-running /amazon-promotions CC would only raise the same finding again, so nothing moves until you send it. Once you have, I run /amazon-promotions CC and work it to a decision.

    This one is stuck waiting on Approve or decline the Chile Crunch BFCM Best Deal and Lightning Deal recommendations (nominations close Nov 13); tentpole deals are never auto-nominated — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x30xm · finding amazon-promotions-cc-bfcm-deals-nomination.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-cc-bfcm-deals-nomination --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-cc-bfcm-deals-nomination --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-cc-bfcm-deals-nomination --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  36. not sized

    mode-7-comp window check + mode7-strategy: our purchase_share on "chili crisp" broke trend downward — find who took it (TST top-3) before the monthly strategy pass.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wytg7 · finding ba-full-matrix-cc-chili-crisp-purchase-share-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crisp-purchase-share-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crisp-purchase-share-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crisp-purchase-share-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  37. not sized

    mode-7-comp window check + mode7-strategy: our purchase_share on "chili crunch" broke trend downward — find who took it (TST top-3) before the monthly strategy pass.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wztrr · finding ba-full-matrix-cc-chili-crunch-purchase-share-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crunch-purchase-share-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crunch-purchase-share-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id ba-full-matrix-cc-chili-crunch-purchase-share-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  38. not sized

    run deal_cover_gate and the margin gate at event fees for B07R7XDXHH, then stage the nomination for operator sign-off before 2026-11-13.

    There is a dated opportunity on this account - a deal, a promotion or a shopping event - and the window to use it closes. Missing it is not a mistake we can fix afterwards. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x3f81 · finding amazon-promotions-CC-bfcm-deal-recommendation.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-CC-bfcm-deal-recommendation --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-CC-bfcm-deal-recommendation --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-CC-bfcm-deal-recommendation --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  39. not sized

    open the promo Issues tab on the Chile Colonial account, decode the error, and stage the fix for operator sign-off before 2026-11-13.

    There is a dated opportunity on this account - a deal, a promotion or a shopping event - and the window to use it closes. Missing it is not a mistake we can fix afterwards. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x3f80 · finding amazon-promotions-CC-bfcm-prime-20pct-suppressed.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-CC-bfcm-prime-20pct-suppressed --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-CC-bfcm-prime-20pct-suppressed --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id amazon-promotions-CC-bfcm-prime-20pct-suppressed --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  40. not sized

    I need you to give me the unit cost (ex-shipping) for CC B07QSSCQ9S. I cannot get this anywhere else — re-running /goal-cascade CC would only raise the same finding again, so nothing moves until you send it. Once you have, I run /goal-cascade CC and work it to a decision.

    This one is stuck waiting on the unit cost (ex-shipping) for CC B07QSSCQ9S — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyx7j · finding goal-cc-readiness-cogs.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id goal-cc-readiness-cogs --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id goal-cc-readiness-cogs --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id goal-cc-readiness-cogs --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  41. not sized

    prepare a mode4 title + description DRAFT for CC for operator approval (LMS: title/bullets/description always need him); no live edit, no price change.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyx61 · finding goal-cc-readiness-copy.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id goal-cc-readiness-copy --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id goal-cc-readiness-copy --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id goal-cc-readiness-copy --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  42. not sized

    I need you to give me approve the mode4 title + description draft before it is published. I cannot get this anywhere else — re-running /mode4 CC would only raise the same finding again, so nothing moves until you send it. Once you have, I run /mode4 CC and work it to a decision.

    This one is stuck waiting on approve the mode4 title + description draft before it is published — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x18dm · finding mode4-cc-copy-readiness.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode4-cc-copy-readiness --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode4-cc-copy-readiness --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id mode4-cc-copy-readiness --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  43. nobody has sized this yet 66 days past due

    DECIDE: CC counts off-Amazon sales in the profit that sets its ad-spend ceiling — the only client set this way TO DO · SOP & Prompts/CLAUDE OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/86eyp97w0 · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  44. nobody has sized this yet 49 days past due

    [MODE 7 Step 3 strategy session] per-client goals, SEO-PPC cross-check, four improvements, CC SB creative C2 — own session after 09-07, land TO DO · SOP & Prompts/CLAUDE OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/86eyup7r3 · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  45. nobody has sized this yet 35 days past due

    CC: 39 mode4/Rufus compliance SKUs have gaps, zero fix packages built TO DO · SOP & Prompts/CLAUDE OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/86eywkn06 · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  46. nobody has sized this yet 24 days past due

    CC catalog hygiene — 5 browse nodes, 3 manufacturer spellings, stray color attr, B07QSSCQ9S outside the variation family TO DO · SOP & Prompts/CLAUDE OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/86eywj6z9 · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  47. nobody has sized this yet 19 days past due

    CC: FBA capacity limit blocks 004-FBA swap (Susie) 2026-10-09 TO DO · SOP & Prompts/CLAUDE OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x040f · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  48. nobody has sized this yet 15 days past due

    CC rank-invest: start 3 terms once restocked + ad-order proof TO DO · Chile Colonial (Chile Crunch)/PPC

    Run the check the ticket itself carries, and close it if it passes: node scripts/checks/rank-invest-close.mjs enabled CC

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/86eyxqtfc · no finding id is attached to it.

    When it is done: the check above is what closes it.

  49. nobody has sized this yet 3 days past due

    CC: B07QSSCQ9S Chile Oil 3-Pack selling at $0 cost - need landed unit cost TO DO · Chile Colonial (Chile Crunch)/OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyrf1 · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  50. nobody has sized this yet 2 days past due

    MODE10: CC — Priority Action "Review Your Account Information" TO DO · Chile Colonial (Chile Crunch)/OPS

    Run the check the ticket itself carries, and close it if it passes: node C:/Users/miraf/.claude/skills/mode10-daily-check/reconcile_findings.mjs --check CC:priority:review_your_account_information

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x2pyb · no finding id is attached to it.

    When it is done: the check above is what closes it.

Nobody has said who owns these 2

Nobody has said who owns these, so they are on neither list above. That is a gap in the job that raised them, not a decision waiting on you.

  1. not sized raised 34 days ago

    NOBODY YET — lms-weekly forwards ads, listing, stock and account-health findings under one name, so its lane is a property of the finding, not of the skill — re-emit it with --operator-lane mine|his

    On the next CC shipment run /send-to-amazon and choose Amazon-optimized splits to avoid the inbound placement fee.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. It is usually spend that produced nothing, a fee charged wrongly, or stock Amazon owes for. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Sellerboard fee breakdown 2026-09-23/24: inbound placement fee $137.35 + inbound transport $319.18; CC P&L 2026-08-28..09-27

    Tracked: on the task board at https://app.clickup.com/t/z8y71wxw94 · finding lms-CC-inbound-placement-fee.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-inbound-placement-fee --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-inbound-placement-fee --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-inbound-placement-fee --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  2. not sized raised 6 days ago

    NOBODY YET — lms-weekly forwards ads, listing, stock and account-health findings under one name, so its lane is a property of the finding, not of the skill — re-emit it with --operator-lane mine|his

    Run /mode7-run on the next Monday cycle to read the 20 Oct cuts and restore exact-term traffic on chili crunch / chili crisp.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Sellerboard P&L 2026-10-25: sessions/day 103 (wk to 4 Oct) -> 74 (19-23 Oct), CVR flat 11.3%; SQP wk 10-17 purchases chili crisp 23->15

    Tracked: on the task board at https://app.clickup.com/t/z8y71x32et · finding lms-CC-sessions-decline-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-sessions-decline-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-sessions-decline-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client CC --id lms-CC-sessions-decline-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

Issues to check

Where this is tracked

38 tasks open on their board, 8 of them past due. The most valuable, worth first:

44 more are in the “On the board” tab above, in the same order.