growth.social-post-weekly·version 1.0.0·draft
Plan and publish the week's social posts
The week's posts are drafted, approved, published on schedule, and their results are recorded before the next cycle.
When to use
Every week, for the company's own social channels. Not for one-off campaign or launch content — use growth.launch-website or a project task when a launch needs coordinated posts. Not for the newsletter — use growth.newsletter; a newsletter may reuse a week's best post, but it is planned and approved separately. If a post mentions a competitor's moves, first check growth.competitor-scan so the claim is current.
Before you start
- The channel list is fixed: which networks the company maintains, and the norm per channel (e.g. LinkedIn
- The owner's off-limits list exists and is current.
- The agent has write access to each channel (or to the scheduling tool the company uses) and to the content log.
What a run requires1
- Approval · S3 · ownerthe run stops until a named person records the decision
Any step can wait until a date and reopens by itself; every closed step leaves evidence (a note, a link, a number).
The trail7 steps
Collect the week's materialagent
Pull last week's results from the content log, anything new from tasks and goals (a shipped feature, a finished job, an open role), and questions customers actually asked this week.
Done when a short list of candidate topics exists, each with its source.
Draft the postsagent
For each channel, draft the posts for the week: text per channel's norm, image or asset where the channel expects one, link target, and the planned day. Mark every factual claim with its source.
Done when a draft set exists — typically 2–4 posts per maintained channel — with each post labelled by channel and day.
Approveownerneeds approval · owner
Approval · S3 · owner — the run stops until a named person records the decision
Show the draft set in one view: post, channel, day, claim sources. The owner edits or strikes posts and names anything newly off-limits.
Done when the owner has approved each post or struck it, and the off-limits list is updated if it changed.
⛔ A post with a price, a legal claim, or a customer's name is never published on the agent's judgement alone.
Schedule and publishagent
Load the approved posts into the scheduler or publish them on their planned days, exactly as approved — no wording changes after approval.
Done when every approved post is live or scheduled, and the live links are recorded in the content log.
Watch and answer within boundsagent
Check comments and messages on the posted items. Answer factual questions using approved wording; forward complaints, negotiation, and anything about a specific customer to the owner the same day.
Done when every comment or message is either answered or handed to the owner, with the handover noted in the log.
⛔ Do not argue with a critical comment in public —
ops.customer-complaintowns that path.Record resultsagent
At the end of the week, enter per post: reach, engagement, clicks, and one line on what the numbers say compared with the trailing four weeks.
Done when every published post has a results row in the content log.
Feed the next cycleagent
Propose 2–3 topics for next week based on S6 (what worked, what did not), and open a task for anything the owner must supply (a photo, a customer quote).
Done when next week's S1 starts with a candidate list ready.
Checks — how we know it worked
- Every post published this week traces to an approved draft in S3 — nothing extra went out.
- Each live post's link opens and shows the approved wording, on the channel it was planned for.
- The content log has a results row for every post, with real numbers, not estimates.
- Zero unanswered comments or messages older than one working day on company posts.
If it goes wrong
| Symptom | Response |
|---|---|
| Owner does not approve by the planned day | Publish nothing; shift the week's posts by a day and tell the owner the new slot — do not approve on their behalf. |
| A post went out with a wrong price or claim | Take it down or correct it in place the same hour, note the correction publicly if the error was visible, record what slipped through in the log. |
| A post is getting hostile comments | Stop replying, hand the thread to the owner, draft one calm factual reply for approval — never a second unapproved reply. |
| A channel shows near-zero reach for 4+ weeks | Say so in S6 with numbers; propose dropping or changing that channel in the monthly review rather than posting into silence. |
| Material for the week is missing | Post less, not filler — one good post beats three placeholders; note the gap and ask the owner for material sources. |
What each step leaves behind
- S1a short list of candidate topics exists, each with its source.
- S2a draft set exists — typically 2–4 posts per maintained channel — with each post labelled by channel and day.
- S3the owner has approved each post or struck it, and the off-limits list is updated if it changed.
- S4every approved post is live or scheduled, and the live links are recorded in the content log.
- S5every comment or message is either answered or handed to the owner, with the handover noted in the log.
- S6every published post has a results row in the content log.
- S7next week's S1 starts with a candidate list ready.
Evidence to keep
The approved draft set (who approved, when) · live links per post · the content log rows with metrics and dates · the off-limits list version in force that week · any comment handed to the owner and its outcome.
How this playbook improves
After every 8 runs ask: planned vs published — where did weeks fall short, and was it missing material or missing approval? Which post formats beat the four-week average, and should the channel norms change? Did any post go out unapproved or with an unsourced claim? A new version changes the step that failed and says so in its change note.
Obligātās sīkdatnes tur sarunu kopā. Analītika ir izslēgta, līdz tu atļauj — tā neliek nevienu sīkdatni un neglabā ierīces identifikatoru.Necessary storage keeps your conversation together. Analytics is off until you allow it — it sets no cookie and stores no device identifier. Ko mēs glabājamWhat we store