---
name: zebrafish-marketplace-listing-pack
description: Create marketplace-ready product image packs with main image, secondary images, infographics, lifestyle shots, what-is-in-box assets, A+ modules, role labels, scope completeness, provenance, and verification.
---

# Zebrafish Marketplace Listing Pack

Use for Amazon listing images, Shopify/Etsy product packs, marketplace
cards, A+ content, product infographics, or a complete product listing
asset set. Do not use for video work, UGC ad variants, or one-off images
with no marketplace role.

Follow the phases in order. Do not skip a phase or a gate. The zebrafish
router skill's Setup and Gates (spend, claim, identity, publish) apply
before and during this playbook.

## Preconditions (MUST)

- Router setup is complete: context script ran, campaign/product knowledge
  loaded, and `../zebrafish/references/tool-belt.md` read (hosted:
  `https://zebrafish.dev/skills/zebrafish/references/tool-belt.md`).
- Required inputs, all present:
  - [ ] Product name and category.
  - [ ] Product image/reference.
  - [ ] Brand constraints.
  - [ ] Target marketplace.
  - [ ] Scope: `main`, `product_images`, `aplus`, or `full_set`.
  - [ ] Claims, ingredients, features, or certifications that are
        allowed.
- If a required input is missing, STOP and ask for it. Do not guess.
  Never infer allowed claims, ingredients, or certifications.

## Phase 1 - Intake and Brief   (gate: brief confirmed)

Restate the brief back to the user before any planning work:

- Target marketplace and scope (`main`, `product_images`, `aplus`, or
  `full_set`), and the asset count that scope implies.
- Product, category, and the reference images in hand.
- Brand constraints and dimension/aspect-ratio requirements.
- Allowed claims, ingredients, features, and certifications, verbatim.
- Approval needs.

STOP until the user confirms scope. Do not plan or spend against an
unconfirmed brief. Scope changes later (single asset to full pack)
re-open this gate.

## Phase 2 - Plan               (gate: spend approved)

1. Collect product facts and reference images into `PRODUCT_FACT_SHEET`.
2. Record the confirmed scope in `MARKETPLACE_SCOPE`.
3. Expand scope into the `IMAGE_ROLE_LIST`: main image, infographic,
   multi-angle, detail shot, lifestyle, what-is-in-box, and A+ modules
   as applicable.
4. Write `COMPLIANCE_NOTES`: marketplace rules that apply, which come
   from source facts or user-approved rules only, per the router claim
   gate.
5. End with a production plan in `ASSET_PLAN`: one entry per role, which
   models (chosen via `list_models`), unit counts, and estimated cost.

STOP for spend approval per the router spend gate before any paid
generation. Approval covers the stated role list only; added roles or
variants re-ask.

## Phase 3 - Produce

1. Generate each role through approved runtime paths only, working from
   the product reference images.
2. Label every output by role, marketplace, and dimensions/aspect ratio
   as it completes.
3. Poll every generation to a terminal state. As each output completes,
   record its provenance fields (provider, model, prompt, generation
   IDs, references, cost) into the delivery document. Draft the
   delivery document during this phase, not after.

## Phase 4 - Verify

Apply the image and marketplace gates from
`../zebrafish/references/verification.md` (hosted:
`https://zebrafish.dev/skills/zebrafish/references/verification.md`):

- Role completeness: every role in `IMAGE_ROLE_LIST` has an output or an
  explicit missing reason.
- Inspect each actual image: main images are product-focused; details
  match the reference product; no artifacts.
- Infographics and A+ modules contain no invented claims, ingredients,
  certifications, or compliance facts — everything traces to
  `PRODUCT_FACT_SHEET` or carries `[unverified]`.
- Style is consistent across the pack unless variants are intentionally
  split.
- Confirm every URL is reachable and cost evidence is captured.

Run `node ../zebrafish/scripts/verify.mjs --strict <delivery file>` (the
router skill ships the same script; agents may use either copy). A
non-zero exit fails the gate: fix findings or move them to `## Unverified`
with a reason, then re-run until it exits clean.

## Phase 5 - Deliver

MUST use the delivery template from `../zebrafish/references/delivery.md`
(hosted:
`https://zebrafish.dev/skills/zebrafish/references/delivery.md`): a
`# Delivery:` title, then `## Outputs`, `## Provenance`,
`## Verification`, `## Unverified`, in that order. URLs first, each
labeled by marketplace role.

After the template sections, append the skill's extra artifacts:
marketplace scope summary, missing-role notes if any, and compliance
notes with unresolved assumptions. Update the `PROVENANCE` and
`VERIFY_REPORT` artifacts to match.

## Studio Artifacts

Create or maintain `PRODUCT_FACT_SHEET`, `MARKETPLACE_SCOPE`,
`IMAGE_ROLE_LIST`, `COMPLIANCE_NOTES`, `ASSET_PLAN`, `PROVENANCE`, and
`VERIFY_REPORT`.

## Provider Policy

- Use approved Zebrafish/FAL runtime provider paths for listing image
  generation.
- Treat external marketplace-card tools as research references until
  provider, rights, compliance, cost, and credential handling are
  approved.
- Marketplace compliance must come from source facts or user-approved
  rules, not generated copy.

## Stop Conditions

STOP and ask before:

- generating paid assets without approval;
- inventing claims, ingredients, certifications, or marketplace
  compliance facts;
- switching scope from a single asset to a full pack;
- using an unapproved external provider.