Weekly content plan

Turns "I should post more" into a week of finished, scheduled posts: a plan the person approves in one look, drafts in their voice on the right channels, checked and queued in their own posting times.

Before you start

1. get_account: time zone, AI drafts left, weekly cap, approval setting, this connection's autonomy.
2. list_channels: which networks, their max_length, media rules, and any needs_reconnect or queue_paused (leave those out and say why).
3. get_posting_schedule per channel: how many free slots the week has. That number, not ambition, sets how many posts to plan.
4. list_posts with status: "scheduled": what's already going out, so the new week doesn't repeat it.
5. list_ideas and list_personas: raw material and the voices to use.

Workflow

1. Agree the frame in one message. Ask only what you can't infer: the goal this week (visibility, leads, hiring, a launch…), anything happening (event, release, news), and topics to avoid. Offer a default.
2. Draft the plan as a table, one row per post: day and slot, channel, pillar, angle (one line), format (story, how-to, opinion, list, case, question), media (none, image, video), and whether it uses an AI draft. Mix formats; never two of the same pillar back to back. State the AI drafts it will use against what's left.
3. Get a yes, then write:
   With the person's own material (notes, an article), create_draft.
   Otherwise generate_draft with a specific idea: the angle, the point, a concrete detail, the audience. One call per idea, with every channel it goes to in channel_ids.
   Tailor per network with per_channel or update_post (LinkedIn can carry the full story; X needs the sharpest line).
4. Polish: read each draft against the writing guidance below; use rewrite_post for targeted fixes ("stronger first line", "cut to 900 characters") and update_post for small edits.
5. Media where the format needs it: see propost-visual-posts.
6. Check: check_post on every post; fix everything it reports.
7. Queue (schedule level and up): add_to_queue fills the person's own times in order. For a fixed moment (an event), schedule_post with an ISO time from suggest_posting_times. On a drafts-only connection, stop here and list what's waiting for approval in ProPost.
8. Report: a short list of what goes out when, on which channel, and what still needs them (photos to add, a fact to confirm).

Writing guidance

• One idea per post. If it needs "and also", it's two posts.
• First line earns the second: a claim, a number they gave you, a tension, a scene. Not "I'm excited to share".
• Specific beats general: "We cut onboarding from 9 days to 2" beats "We improved onboarding".
• End with something to do or think about, not "Thoughts?" every time.
• Weekly rhythm that works for most people: one story, one how-to or lesson, one opinion, one proof (result, case, behind the scenes), one conversation starter. Scale down to the slots available.

Example plan row:

Guardrails

• Don't schedule anything the person hasn't seen in the plan.
• Never publish_now as part of planning.
• Don't exceed the weekly cap or the drafts left; plan within them.
• No invented results, numbers or quotes: mark [add your number].
• Respect paused queues and reconnect states; never work around them.

If something fails

• quota_exceeded: write the remaining posts yourself with create_draft.
• weekly_limit: keep the rest as drafts, tell them which and why.
• no_slots / queue_paused: offer exact times (schedule_post) or, at schedule level, add times with set_posting_schedule.
• too_long: shorten and check_post again.
• Anything else: see ../CONVENTIONS.md.