Skip to content

Week of Posts

Read by connected AIs with get_playbook and id week-planner.

A week of drafts, spread across the week, one approval each.

Use for a week or more of posts planned day by day. Not for today’s ideas or one post.

The user might say: “Plan my next seven days of posts from Xholic’s plan for this week, my analytics and my queue. Draft each slot as its own post, one option per slot titled with the day, save it into the plan, and ask before scheduling anything.”

  1. Xholic’s plan for this week: each slot’s day, time, sub-topic, why and draft, and the week’s test. Work from it; don’t build a separate list. Call get_week_plan.
  2. What’s already queued, so nothing doubles up. Call get_queue with {"view":"queued"}.
  3. Check what the user’s Workers already wrote: ready-made drafts, free to use. Call get_worker_drafts.
  4. Get material in the user’s voice (proven posts, their winners, saves, recent posts to avoid repeating). Call get_writing_kit with {"topic":"<each slot's sub-topic>"}.
  5. For each post, find proven posts on its idea near the account’s size, ranked by how far they beat their author’s usual. Add 1–4 keywords so it can search live X when the library is thin. Call search_inspiration with {"query":"<the post's idea>","keywords":"<1-4 words>"}.
  6. Write each post yourself from one source post’s shape (hook, structure, kind of ask): one idea each, the user’s voice, no links, no facts that aren’t in the user’s data.
  7. Check every draft before showing it, with the id of the post it was built from; fix what it flags. Call check_draft with {"text":"<post>","sourcePostIds":"<source post id>"}.
  8. Save each slot’s draft into the plan. Call update_plan_slot with {"slotId":"<slot","text":"<post>"}.
  9. Show one post per slot, titled with its day. Approve each one only after the user says yes to that post (never several on one yes); test slots start the week’s test. Call approve_plan_slot with {"slotId":"<slot"}.