Step 1
Write out the daily routines as they happen today with who performs each one, the order they follow, the inputs used and the output handed to the next person.
Daily store routines live in one person's head, and coverage collapses when that person is away. In this case, the immediate task is to coordinate daily store operations through explicit rules. The workflow should turn the actual task list and current owners into written rules with defined outcomes, so handoffs survive staff changes.
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 coordinate daily store operations through explicit rules.
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 daily routines as performed today with each performer, the order they follow, the inputs and outputs at every handoff, the merchant's named fallback owners and the parts requiring judgement]. Turn each routine into a rule naming its owner, the condition that starts it, the defined outcome that marks it done and the parts requiring human judgement, and settle any two rules touching the same record by recording which one takes precedence.
Return an operations rule set with handoff points 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.
Write out the daily routines as they happen today with who performs each one, the order they follow, the inputs used and the output handed to the next person.
Turn each routine into a rule naming its owner, the condition that starts it, the defined outcome that marks it done and the parts requiring human judgement, and settle any two rules touching the same record by recording which one takes precedence.
Deliver the rule set with handoff points, precedence notes and a fallback owner per rule, then walk one full day against it and confirm every handoff has a named owner and an output that was actually produced.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
The ones that break when a particular person is away, because those carry knowledge nobody else holds. Among them, rules with stable inputs and reversible outcomes can then be handed to automation.
Mark the decision point and the person who makes it rather than trying to encode it. A rule that silently guesses at a judgement call produces confident errors.
Record the conflict and the precedence chosen, so the outcome does not depend on which one happened to run first. Undocumented precedence makes the same day produce different results.
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.