Build a founder posting system

Needs and produces

You need a Tone of Voice page or an existing account brand voice, business context that supports any claims, and a clear topic or audience. A missing connected account does not block drafting. When the account lacks a saved voice, draft from the Tone of Voice page and say so. Before adding a topic, inspect the existing drafts so a revision is used for the same topic rather than a near duplicate.

The play produces two weeks of dated drafts with a call to action, channel-specific copy, and a visible review surface. It can bind more than one named account for a channel, or every connected account when the request explicitly says all accounts. It does not produce a provider delivery receipt, a published post, or a promise that every channel has the same character limit.

Ground each draft in Context and channel rules

Read workspace knowledge before writing: the audience, business facts, and tone. Claims about the business need saved workspace evidence or a dated source. A social draft should not invent a customer number, a result, or a named company to make a hook land. For an existing topic, open and revise the saved draft, preserving copy and formatting that were not requested to change.

Read the channel registry before writing. It holds the actual maximum content length for the account. X counts weighted characters, including links, and each thread post must be checked on its own. LinkedIn has a three-thousand-character limit and its final line normally opens with an ask verb or asks the reader a real question. A LinkedIn close that fails that rule is refused with linkedin_cta_required.

LinkedIn's first roughly 210 characters need to earn the feed click with a specific claim, scene, question, or tension and a bridge to the payoff. X needs a strong first five to eight words. Write one core idea per post. Use actual facts, varied sentence length, and line breaks that clarify a turn. Do not add hashtags or emojis unless asked, and resolve every mention before scheduling.

Draft a reviewable calendar

Build the content plan as a set of individual drafts. Each draft can carry several channels and several accounts, with the LinkedIn body, X post or thread, and any other channel payload in that one object. When a request covers LinkedIn and X, do not create parallel drafts with the same idea. Bind only the accounts named by the user, then inspect the saved result in Calendar.

A LinkedIn post uses short paragraphs, specific evidence, and a closing ask that gives something back. An X thread exists only when the idea has sequential beats. Its first post carries the whole promise, the later posts add a distinct point, and the close resolves the opening tension. A one-post idea stays one post. The channel skills prohibit filler phrases and unsupported numbers, so editing tightens an existing draft instead of replacing its voice with generic copy.

1. 1

   Read Context and existing drafts

   Use social to inspect saved business facts, voice, and draft state. Check Calendar for a same-topic draft before creating another.
2. 2

   Load each channel skill

   Use linkedin-posts or x-posts for the selected channels. Architect reads the channel registry instead of assuming a length limit.
3. 3

   Create one shared draft per idea

   Add the named channels and account bindings to one draft. Put each channel's copy in its payload and give the draft a planned date only when scheduling was requested.
4. 4

   Review rendered copy

   Read hook, CTA, character limit, mentions, and formatting. The operator sees saved drafts in Calendar and can revise an individual channel without rewriting the others.
5. 5

   Read back the saved state

   Report the draft links, channels, accounts, dates, and what remains: review, schedule, or a separately requested publish action.

Credits and leading metric

This catalog play uses social draft and schedule work only, never publication. Drafting needs no system review step. A planned date is an optional field on a draft, not a hidden posting action. If a later action involves an external provider or paid operation, inspect its current estimate and execution result rather than inferring a standing cost from the content plan.

The leading metric is a two-week calendar of saved drafts that fit the voice and have a channel-valid hook, clear core idea, and appropriate close. Report drafts created or revised, channel and account bindings, planned dates, unresolved facts, and whether the result is only drafted or also scheduled. Calendar is the visible checkpoint for this play.

When it goes wrong

If a claim is not in Context or a dated source, omit it and name the missing evidence. If a LinkedIn draft fails with linkedin_cta_required, revise the final line into an ask verb or a question addressed to the reader, then save and read back the draft. If X copy exceeds the account's current limit, cut support or split a genuine sequential idea into numbered posts rather than padding or guessing.

An unresolved mention must be resolved before scheduling. Do not send it to a provider as literal text. When an edit to one channel appears to alter another, read the saved draft, compare every channel payload, restore the unchanged copy if needed, and read again. A missing account blocks publishing, not drafting. Keep the draft and report the connection needed.

If a request says publish, that is a new delivery request outside this play. Show the final channel copy and read the delivery result after it occurs. Do not call a draft published because it has a date, a Calendar entry, or a completed writing task.

Read the current draft before a revision. Preserve its unrequested formatting and channel payloads. Keep the named title or topic intact. Report what the saved result proves. A request is not a delivery receipt. A schedule is not a published post. A publish result needs its own readback. This separation prevents accidental duplicate public content.