Content moves between draft, review and published with no agreed rule for what advances it. In this case, the immediate task is to design a content publishing workflow with status tracking. The output should attach checks, approvals and failure handling to each status transition.
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 design a content publishing workflow with status tracking.
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 full status list with the evidence required for each status change and the approving role, the field and asset checks per status, each item's current status, destination and target publish window, and the previous status and timestamp used for rollback]. Advance an item only when every check for that transition passes and the approval for it is recorded, run the checks in one fixed order so the failure reported first is the one that blocks, and on any failure write the check, the reason, the timestamp and the reviewer to the item's log while leaving it in the status it already held, with no automatic retry that could publish a piece twice.
Return a content workflow and sample output batch with the status rules verified against the merchant's 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 every status a content item can hold in this store with the evidence required to leave each one and the role whose approval records that evidence, then attach to the batch the current status of every item, its destination and target publish window, the field and asset checks defined for each status, and the previous status and timestamp to which an item returns when a transition is rejected.
Advance an item only when every check for that transition passes and the approval for it is recorded, run the checks in one fixed order so the failure reported first is the one that blocks, and on any failure write the check, the reason, the timestamp and the reviewer to the item's log while leaving it in the status it already held, with no automatic retry that could publish a piece twice.
Deliver a content workflow and a sample output batch showing each item with its status, the checks passed, the approver, the failure reason where one was recorded and the rollback values, then reconcile the count of items in each status against the merchant's content inventory, confirm every published item appears once at its destination, and confirm every held item carries a named blocking reason.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Each transition names the evidence it needs before it can run, such as the completed required fields, the asset attached and the approval recorded for it. Evidence must be recorded, not asserted verbally, so the log can be replayed later; where the merchant has not defined a check, that transition is listed as undefined rather than assumed to pass.
Approval is a separate role from authorship in the workflow the merchant defines, and the approver is recorded on the item. Keeping the roles apart gives the check an independent reviewer; where one person legitimately holds both, the merchant decides it explicitly and the log still shows who approved, so the exception stays visible rather than hidden.
A rejected transition leaves the item in the status it already held and writes the blocking check, the reason and the timestamp to its log. Nothing advances without evidence and no retry runs automatically, because an automatic retry could publish a piece a reviewer has already refused; the item moves only after the named check passes on a later run.
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.