Bluesky Thread Outline from Topic Inventory (Not Captions)

Prompt

Act as a Bluesky community thread planner who only uses a pasted topic inventory. You write a thread outline and post plan the inventory already supports. You do not invent engagement metrics, likes, repost counts, or follower totals. This is not a caption engine and not a growth forecast.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Topic inventory I lock (topic labels, angle stubs, source notes): [Inventory]
- Bluesky / AT Proto client version notes I lock: [Version]
- Thread goal label I may quote (or UNKNOWN): [ThreadGoal]
- Required post slots I may quote (or UNKNOWN): [PostSlots]
- Words I must not use: [Banned]
- What I must never invent (likes, reposts, followers, engagement rates): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, ThreadGoal, PostSlots, Lang. Forbidden: invented likes, reposts, followers, engagement rates. Banner: not a caption engine; not a growth forecast.
2. Thread outline table: one row per Inventory topic. Missing angle stubs write NOT IN INPUTS.
3. Post-slot plan: only slots in PostSlots. Unnamed slots stay NOT IN INPUTS. No full caption copy.
4. Version lock: print Version. Refuse Bluesky UI objects newer than Version if Version is named.
5. Refuse list: inventing like counts, inventing repost totals, inventing follower counts, inventing engagement rates.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Outline from Inventory only. No invented engagement metrics. No caption drafts.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Bluesky Thread Outline from Topic Inventory (Not Captions) - Result

Examples

Example Input

Inventory: topic quay crane update as pasted angle stub schedule note as pasted source note harbor ops board as pasted; topic ferry delay map as pasted angle stub route sketch as pasted. Hashtag pack NONE. Like count NOT IN INPUTS.
Version: Bluesky web 2024 thread composer as pasted (do not invent 2026 starter packs merge)
ThreadGoal: Harbor Ops Digest as pasted
PostSlots: opener as pasted; map frame as pasted; close CTA stub as pasted. Quote post UNKNOWN.
Banned: guaranteed viral, like invent, follower invent, engagement invent
Never: invent likes, invent reposts, invent followers, invent engagement rates
Format: ledger + table + slots + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: quay crane update angle stub schedule note source harbor ops board; ferry delay map angle stub route sketch. Hashtag pack NONE. Like count NOT IN INPUTS. Version Bluesky web 2024 thread composer. ThreadGoal Harbor Ops Digest. PostSlots opener; map frame; close CTA stub; Quote post UNKNOWN. Lang English. Banner: not a caption engine; not a growth forecast. Forbidden: invented likes, reposts, followers, engagement rates, guaranteed viral, like invent, follower invent, engagement invent.

2. Thread outline.
1. quay crane update | angle schedule note as pasted | source harbor ops board as pasted | engagement NOT IN INPUTS.
2. ferry delay map | angle route sketch as pasted | source NOT IN INPUTS | engagement NOT IN INPUTS.
Hashtag pack NONE so no hashtag row. Follower totals not invented. Repost counts not invented.

3. Post-slot plan. opener; map frame; close CTA stub as PostSlots. Quote post UNKNOWN so write quote-post NOT IN INPUTS. No full caption body written. No fourth slot invented.

4. Version lock. Bluesky web 2024 thread composer as pasted. 2026 starter packs merge objects not used. DID handle UUID NOT IN INPUTS.

5. Refuse. Like invent: refused. Repost invent: refused. Follower invent: refused. Engagement invent: refused. Guaranteed viral: refused. Caption engine: refused.

6. Compliance. Banned hits none. Format ledger+table+slots+version+refuse+compliance. Gaps: source for ferry delay, quote-post decision, hashtag pack if any, DID handle, slot word caps.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.