---
name: create-social-media-posts-per-platform
description: "Turn one useful idea into posts for the channels you use. Match the words and media to each place."
category: Content Factory — Process
stage: Process
definitive_article: GAP — to be written
status: needs-work
---

# Create social media posts per platform

Your customers may see the same idea in more than one place. This guide helps you shape that idea for each channel you choose. Start with one true point and the accounts in your plan.

**The path:** Source idea → Chosen channels → Clear copy and assets → Posting handoff.

**Use this when:** Processed content needs ready-to-use social copy and assets for specified channels.

## Inputs
- The checked source article or draft, clips/cards and [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/) brief.
- The exact in-scope Facebook Page, LinkedIn profile/Page, Instagram or X account; do not assume all four are used.
- Verified handles, voice, rights, canonical destination and current format/composer limits.
- A tracker with draft/published state, posting owner and existing schedule if any.

## First-run prompt

> Adapt this checked content for the exact channels in my plan. Keep the real voice and facts, verify handles and link behavior, and return copy plus media for each account. Save true draft/scheduled/live states. Use existing posting authority where given, but do not invent channels, tags, results or a timer.

## Steps
1. Choose the platforms from the real audience and plan. The goal is useful content where readers are, not four mandatory rewrites for an absent account.
2. Write the core insight in one sentence, then adapt its framing. Retain the same facts and source limit across every version; different wording must not become different claims.
3. For Facebook, use clear conversational context and a real visual when appropriate. A Page and a restricted group have different readers and rules; do not address an assumed 44,000-person audience.
4. For LinkedIn, frame the practical lesson for the actual profile or Page voice. For Instagram, make the visual understandable and support it with clear caption text. For X, make the single point or thread useful without arbitrary fragments. Check current composer limits rather than hardcoding every future limit.
5. Use verified relevant mentions only when appropriate and allowed. Do not tag every named person automatically, invent handles or imply a relationship from a tag.
6. Add the checked canonical article link where the chosen placement supports it. A draft URL remains a draft dependency. If a caption needs a bio/link route, verify that actual route instead of promising a clickable link that is not present.
7. Proofread names, claims, captions, media crops and destination. The exact same concise sentence may be appropriate on two channels; distinct usefulness matters more than cosmetic rewriting.
8. Save each platform’s final copy, asset, target account, publication state and next owner. Carry out scheduling/posting only if already part of this job, using the maintained Post task; then verify the actual scheduled or live state separately. A future schedule needs a named first-firing receiver and check.

## Definition of done (QA checklist)

- [ ] Only requested relevant channels are included, with correct account/voice.
- [ ] Each version teaches the source-backed point and has working appropriate media/links.
- [ ] Tags and claims match evidence and platform context.
- [ ] Draft, scheduled and live states are explicit; no automatic schedule or engagement is claimed.

## Example(s)

**Fictional teaching example — no social posts were made.** The shared lesson is that clear photos help a bike shop prepare.

**Facebook draft:** “Send a full view of the bike and a close-up of the issue. Add when it happens. Those details help us prepare for your visit.”

**LinkedIn draft:** “A useful intake request tells the customer exactly what to send. Our sample bike checklist asks for two views and one short note, while keeping the inspection step clear.”

The Instagram card shows “Whole bike / Close-up / When it happens.” Its link route stays pending until the real account is known. No X draft is required if X is outside this job’s plan.

## Handoff and Content Factory context

The posting owner receives each prepared package. Use [Post to the Facebook Page](https://local-service-spotlight.github.io/task-library/?task=post-to-facebook-page#task-post-to-facebook-page) and [Post to LinkedIn](https://local-service-spotlight.github.io/task-library/?task=post-to-linkedin#task-post-to-linkedin) for those selected channels. Other channels use their actual maintained account workflow.

Produce supplies the real source. **Process**, this stage of the [Content Factory](https://blitzmetrics.com/content-factory/), turns it into useful finished assets. Post saves or publishes them on the agreed channels. Promote tests and distributes suitable work within its own scope. The handoff above names this task’s actual next step; catalog neighbors alone are not prerequisites.

## When this runs

Per content package. Reuse the project’s real calendar if authorized; no universal recurring cross-post job is created.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Process
- **Importance:** 5/5 `●●●●●` — frequency 5, revenue 4, gating 2 (runs every factory cycle or weekly; creates the asset ads amplify)
- **Suggested previous station:** `grade-article-using-jennifer`
- **Suggested next station:** `write-email-newsletter-from-video-key-insight`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Process-stage artifact examples include `transcript.md`, `gct.md`, `article.html` (or a staged draft), `clips/`, or `04-Promote-Creatives/`. These are examples, not requirements for every task. Follow this task's actual Inputs and Handoff sections for the required output, evidence, and next owner. Pass the files or records, not one vendor's memory.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Dedicated canonical article: not mapped in this source record. Use the maintained owned training below until that article gap is reviewed.
- Exact task: [Create social media posts per platform](https://local-service-spotlight.github.io/task-library/?task=create-social-media-posts-per-platform#task-create-social-media-posts-per-platform)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Entity linking: choose the right person, company or guide](https://blitzmetrics.com/entity-linking/)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- Dedicated article is unmapped; real account IDs, other-channel workflows and current composer behavior need project-specific checks.