01
Step 1
Collect the campaign dates and the product stories planned for the period, the channel mix with each channel's posting limit, the brand or seasonal moments already fixed, the assets available per story, and the person who owns each story.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Plan a coherent social content calendar
A merchant has several product stories to run this month and keeps discovering afterwards that two of them landed in the same week. In this case, the immediate task is to plan a coherent social content calendar. The workflow should produce dated slots with a named owner and asset status per post, spaced so adjacent themes do not repeat.
Topic
Social Media Content Creation
Target keyword
shopify social media content calendar
Copyable AI prompt
A prompt you can drop directly into Spark
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.
ai-prompt.txt
Act as a Shopify operations specialist.
Help me plan a coherent social content calendar.
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: [campaign dates and the product stories planned for the period, the channel mix with each channel's posting limit, fixed brand or seasonal moments, asset availability per story, and the owner of each story]. Place each story in a dated slot while checking that no two adjacent slots carry the same theme or the same product, spreading repeated themes across the period, holding back the unscheduled capacity the merchant wants per week for in-period changes, and marking any slot whose asset is not ready with the date it is expected.
Return a dated calendar with owners and asset status 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.How to solve
A recommended resolution workflow
Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
02
Step 2
Place each story in a dated slot while checking that no two adjacent slots carry the same theme or the same product, spreading repeated themes across the period, holding back the unscheduled capacity the merchant wants per week for in-period changes, and marking any slot whose asset is not ready with the date it is expected.
03
Step 3
Deliver a dated calendar with one row per slot naming the theme, the channel, the owner, the asset status and the claim the post will carry, verify that no slot exceeds the channel's stated posting limit and no owner holds more slots in a week than the merchant's stated capacity, and list the reserved slots kept free for late changes.
FAQ
Common questions when running this scenario
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
How far ahead should the calendar run?
The horizon the merchant can actually staff and keep accurate, since a short calendar that stays true beats a long one nobody updates. It is extended when the asset status shows stories are ready further out, not simply because the period ended.
Can the same story run in back-to-back slots?
Only when a campaign requires it, such as a launch sequence, otherwise adjacent slots alternate themes so returning followers see variety. Spacing also protects a story that underperforms, because the second slot can still be changed before it runs.
How are urgent product changes absorbed?
Through the unscheduled capacity held back in each week, so the slot is filled from the reserved list rather than by dropping a planned post. Where the change outruns that capacity, the least time-sensitive story moves out and the move is recorded on the calendar.
Related scenarios
Continue with adjacent or same-topic scenarios
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Next step
Want these AI scenarios embedded directly into daily operations?
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.