Step 1
List the recurring tasks with the inputs each depends on, the condition under which it should run and the person who performs it by hand today.
The team spends hours each week on the same copy-paste chores that follow predictable patterns. In this case, the immediate task is to automate recurring operational tasks. The workflow should identify which of the merchant's repeating tasks have clear inputs and run conditions, then spec the action, its log entry and how often it may fire.
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 automate recurring operational tasks.
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: [each recurring task with its inputs, run condition, current manual performer, the log entry it must write and the merchant's maximum runs per period]. Specify for each the action to perform, the log entry it must write, the idempotency check that keeps a repeated event from producing a second outcome, and the maximum number of runs allowed in the period the merchant sets.
Return a task automation spec with run limits 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 recurring tasks with the inputs each depends on, the condition under which it should run and the person who performs it by hand today.
Specify for each the action to perform, the log entry it must write, the idempotency check that keeps a repeated event from producing a second outcome, and the maximum number of runs allowed in the period the merchant sets.
Deliver the task automation spec with the action, log fields, run limit and partial-failure behaviour, then compare the log entries from the first run against the count of records the task should have touched and confirm the two match.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Those with a stable input, a condition that can be tested and an outcome that can be reversed. A task needing judgement each time usually costs more to supervise than to do by hand.
By checking a run log for the same record and event before acting. Retries and repeated events are normal, so without that check the store gets two of every outcome.
Follow the behaviour written in the spec, either rolling the partial run back or leaving it with the failed record identified. Silently continuing hides a mixed state that is hard to detect later.
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.