# Social Batch Drafting

> Draft a 9-post social batch (3 days × 3 platforms) from any source. Voice rules enforced before drafting begins. Approved batch becomes the durable handoff to the queue skill.

**Skill · v1.0 · Updated 2026-05-03**

Social Batch Drafting is a skill for producing a complete 9-post social batch (3 days × 3 platforms) from any source artifact, with voice rules enforced as pre-flight gates and prior-batch threading running by default. The output is an approved batch markdown file ready for the downstream queue skill to ship.

## Install

### Claude Code (CLI / WSL / Git Bash)

```
/plugin marketplace add https://www.infinitegameos.io/marketplace.json
/plugin install social-batch-drafting@igos-library
```

### Claude Code (VS Code)

[Install in VS Code](vscode://anthropic.claude-code/install-plugin?plugin=social-batch-drafting&marketplace=https%3A%2F%2Fwww.infinitegameos.io%2Fmarketplace.json)

Opens the Claude Code plugins dialog with the marketplace and skill prefilled. Requires the Claude Code VS Code extension installed and signed in. Or paste the snippet below into `.claude/settings.json` for VS Code, JetBrains or any setup that prefers manual config:

```json
{
  "extraKnownMarketplaces": {
    "igos-library": {
      "source": {
        "source": "url",
        "url": "https://www.infinitegameos.io/marketplace.json"
      }
    }
  },
  "enabledPlugins": {
    "social-batch-drafting@igos-library": true
  }
}
```

### Direct markdown URL

```
curl https://www.infinitegameos.io/markdown/skills/social-batch-drafting
```

Or send `Accept: text/markdown` to https://www.infinitegameos.io/skills/social-batch-drafting

### Cursor

```
curl -O https://www.infinitegameos.io/install/cursor/social-batch-drafting.mdc
```

### Aider, Cline, any agent with --read

```
curl -O https://www.infinitegameos.io/markdown/skills/social-batch-drafting
aider --read social-batch-drafting.md
```

## Definition

Social Batch Drafting takes a single source (an article, a session reference, a workshop campaign, a product page) and produces nine posts: three days, three platforms per day. The skill enforces voice rules before drafting begins and re-runs the sweep against the produced copy before presenting it to the operator. Forward-reference threading runs automatically when a series predecessor is named; light breadcrumb weaving runs by default for one-off batches. Anchor arcs (multi-batch escalations like reveal arcs, seat-count countdowns or product hints) carry state across batches so the next installment honors what came before. The output is an approved batch markdown file that becomes the durable handoff artifact for the Social Batch Queue skill. Voice and threading discipline live here; execution and scheduling belong downstream.

## The 9-post structure

Three days. Three posts per day. Three platforms per post (Instagram, Facebook, LinkedIn by default; Threads, Substack notes and other text-first surfaces substitute as the operator chooses). Day 1 is a hook that opens a tension or scene. Day 2 is an 8-slide carousel that walks the full arc: cover, foundation, distinction, core practice, second layer, fear or turn, connection to the parent concept, close. Day 3 is a direct invitation with an anchor seed and references to prior installments. The carousel exports as 8 PNG pages for Instagram and Facebook plus a single PDF document for LinkedIn.

The three days move from tension to architecture to invitation. Each day is standalone-capable; together they tell a complete arc. Headlines on Day 1 and Day 3 end with a period (or a question mark for questions) and stay between three and six words. Carousel slide headings stay punchy and pull from source content rather than getting invented at draft time.

## Voice rules and threading as pre-flight discipline

Voice rules run as gates, not suggestions. Em dashes, missing contractions, Oxford commas, internal names in public copy, fabricated anecdotes, pure-negation framing without an affirmative reframe: each gets caught before the draft reaches the operator. The skill ships with the author's defaults; operators layer their own rules via voice addenda. The structural enforcement (sweep before drafting, sweep after drafting, halt on violation) is the contribution.

Forward-reference threading is the second layer of discipline. When a series predecessor is named, all platforms get the thread, not just LinkedIn. The Day 1 opener names what came before and where the batch is now. The carousel close threads the accumulation. The Day 3 action references prior installments before the anchor seed. When no series exists, the skill still surfaces light breadcrumbs from recent batches: a quotable phrase, a sensory image, a recurring opening register. The principle: every social post knows what came before it.

## Use Cases

**Article-driven batch from a polished long-form piece**

A long-form article ships and the operator wants a 9-post sequence carrying the same thesis to social. Social Batch Drafting reads the article, extracts the load-bearing sensory moments and the lines that would land verbatim, threads any prior-batch references and produces the full 9-post draft. The operator reviews, approves, hands off to the queue skill for scheduling.

**Workshop or product-launch campaign with seat-count escalation**

A workshop runs in three weeks. The operator wants an arc of three batches across the campaign window, each one escalating the seat-count language. Social Batch Drafting reads the prior batch's anchor arc state verbatim and proposes the escalated phrasing for this batch before any copy is written. Continuity becomes structural rather than rememberable.

**Multi-batch series with forward-reference threading**

A content arc spans many weeks. Each batch references prior installments to make the arc visible to the audience. Social Batch Drafting names which batches to thread before drafting, then drafts the Day 1 opener explicitly first. The accumulation becomes part of the story across LinkedIn body copy, carousel close slide and Day 3 action.

**Freeform sequence batch with light breadcrumb weaving**

A one-off batch with no formal series. The skill still scans recent batches and surfaces 1 to 2 candidate breadcrumb lines: a quotable phrase, a recurring image, a voice anchor. The operator chooses whether to weave them. The principle holds even outside formal series: every batch knows what came before it.

**Workshop attendee-driven sequence with date specificity**

A live workshop produced themes worth carrying forward into public batches. Social Batch Drafting takes a workshop-summary or topic-harvest doc as the source, applies a voice addendum requiring date specificity (specific weekday and date rather than "this weekend") and produces the batch with workshop continuity preserved.

## FAQ

**Why a skill instead of a memory or a checklist?**

Memories drift. Checklists get skipped under deadline pressure. A skill makes the pre-flight structurally impossible to skip: the voice sweep gates are explicit steps, the threading scan runs by default, the approval gate is a hard pause. The discipline becomes the file rather than the operator's willpower.

**What if my voice rules are different from the defaults?**

Layer your own via voice addenda. The skill's structural enforcement (sweep before drafting, sweep after drafting, halt on violation) holds. The specific rules are operator choice. Some rules ship as defaults because they catch common failure modes (em dashes reading AI, Oxford commas drifting in via dictation tools); replacing them is a deliberate operator decision.

**How does forward-reference threading work in practice?**

When a series predecessor is named, the skill reads its anchor arc state verbatim, names which prior batches to thread before drafting and writes the Day 1 opener explicitly first. All platforms get the thread, not just LinkedIn. Temporal language carries the references ("a few weeks ago I wrote", "last week", "this week") rather than internal names.

**What happens if the post-draft sweep catches a voice violation?**

The skill halts at Step 8 and routes back to Step 7 for the affected post. The draft does not reach the operator until all gates pass. This is non-negotiable; presenting a draft with violations forces the operator to do the sweep manually, which defeats the skill's purpose.

**Does this skill schedule the posts?**

No. Drafting produces the approved batch file; the Social Batch Queue skill consumes it and ships through the operator's scheduling tool. The boundary is firm. Voice and copy are Drafting's responsibility; image generation, asset staging and scheduler integration belong downstream.

## Related

- [Social Batch Queue](https://www.infinitegameos.io/skills/social-batch-queue)
- [Pending Plan Implementation](https://www.infinitegameos.io/skills/pending-plan-implementation)
- [Plan Challenger](https://www.infinitegameos.io/skills/plan-challenger)

---

Social Batch Drafting pairs with Social Batch Queue. Drafting produces the approved batch; Queue ships it as scheduled posts. The two work as a flywheel. The Sovereign Life Playbook is the upstream design frame for which work is worth distributing in the first place.

[See the Sovereign Life Playbook](https://sidequesthq.co/products/sovereign-life-playbook)

---
*[Infinite Game OS](https://www.infinitegameos.io) · [Skills](https://www.infinitegameos.io/skills) · [Social Batch Drafting](https://www.infinitegameos.io/skills/social-batch-drafting)*