Build a Topic Cluster Around a Core Subject

    You are a content strategist who builds coverage of a topic rather than a pile of posts.

The core subject I want to own: {{topic}}
Who I'm writing for, and what they're trying to do: {{audience_and_goal}}
What I sell, and how this topic connects to it: {{commercial_connection}}
What I've already published on this: {{existing_content}}
My realistic publishing capacity: {{capacity}}
Where I have genuine expertise or proprietary information: {{unique_knowledge}}

Produce:

**Scope the topic honestly.** Is {{topic}} the right size for a cluster? Too broad and I'll never cover it credibly against sites with more authority; too narrow and it's one article. If it's wrong-sized, propose the version I could actually own — usually a narrower topic where {{unique_knowledge}} gives me an advantage.

**The pillar.** The central page: what it covers, how it's structured, and what job it does. It should be genuinely comprehensive on the main question and link out to the depth rather than containing all of it.

**Supporting articles.** For each: the working title, the specific question it answers, the search intent behind it, how it differs from its neighbours, and its priority. Cover the topic's real shape — the definitional questions, the how-to questions, the comparison and decision questions, the problem and troubleshooting questions, and the objection questions people ask before buying. Most clusters over-invest in the first group and skip the last two, which are the ones closest to revenue.

**Commercial mapping.** For each piece, how far it sits from a purchase decision, and what the realistic next step is for a reader. Given {{commercial_connection}}, flag the two or three pieces that justify the whole cluster commercially — and be honest about which are pure top-of-funnel that may never convert directly.

**Link structure.** Which pieces link to which, and why. The pillar links down to each supporting piece; supporting pieces link up to the pillar and sideways to their nearest neighbours. Give me the actual map, and note that this structure is what makes a cluster function rather than the label.

**What to write first.** Sequenced for {{capacity}}, front-loading the pieces that either serve {{commercial_connection}} or that other pieces depend on.

**Against what exists.** From {{existing_content}}: what's reusable, what should be updated into the cluster, and what should be consolidated or removed rather than left competing with the new work.

**Where I can be different.** For each piece, how {{unique_knowledge}} makes my version worth reading rather than a restatement of what's already ranking. If a piece has no answer to that, mark it — a summary of what everyone else has said is unlikely to earn traffic or citations in a market where that content is now generated at zero cost.