Step 1
List the essential questions for this specific product from its support records and specification, and open the page content with its section names so every question can be located against the copy that exists.
New listings ship with descriptions written before anyone decided what the page must explain. In this case, the immediate task is to check whether a product page answers essential buyer questions. The workflow should produce a checklist marking each question answered, partial or absent, naming the section where the answer belongs and the copy still missing.
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
Act as a Shopify operations specialist.
Help me check whether a product page answers essential buyer questions.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [the product's essential questions from support records and specification, and the page content with section names]. Mark each question as answered, partial or absent, name the exact section where the answer should live, and for every partial answer record precisely which part of the specification is missing from the copy.
Return a checklist of the gaps with the copy each one needs, verified against the supplied records for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
List the essential questions for this specific product from its support records and specification, and open the page content with its section names so every question can be located against the copy that exists.
Mark each question as answered, partial or absent, name the exact section where the answer should live, and for every partial answer record precisely which part of the specification is missing from the copy.
Deliver the checklist with the missing copy each gap needs, then verify that every listed question carries exactly one verdict and that answered, partial and absent counts sum to the question total.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
When the page addresses the topic but leaves out a part that changes the decision, such as a delivery window without the cutoff, the verdict records exactly which piece of the specification is missing; partial is a distinct verdict because the fix is targeted copy, not a new section.
Because the checklist doubles as a copy plan: an absent question is paired with the section where its answer belongs, so the writer knows whether to extend existing copy or add a block, and no answer is written into a section buyers skip.
It works as a base of universally essential questions, but each product adds its own from its specification and support record, since sizing, compatibility and care questions differ; reusing the base without extension is what let pages ship with unexplained terms.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.