Help me create a Substack post for [TARGET READER] around the target keyword or reader question [TARGET KEYWORD OR QUESTION]. My point of view and thesis are [THESIS AND ANGLE]. Use only these source notes, experiences, data, and links: [SOURCE MATERIAL]. The desired format and length are [FORMAT AND LENGTH], and I want readers to take this action or leave with this result: [READER TAKEAWAY]. First, propose one working headline, one subheadline, and a detailed outline. The outline must include: a specific opening tension or observation; the reader’s real problem; a clear thesis; 3–5 sections that each advance the argument with evidence, examples, or a useful method; one limitation, counterpoint, or condition where the advice does not apply; and a conclusion with a practical next step. Then write the full post in the requested length. Use the target keyword naturally in the headline, opening, and at least one relevant subheading only if it reads naturally. Prioritize reader intent over search phrasing. Distinguish my observations from sourced facts, and attribute statistics, claims, and quotations to the source material I supplied. Do not invent reporting, firsthand experience, examples, links, statistics, quotations, expert views, or a certainty level stronger than the evidence supports. Avoid an empty introduction, generic trend commentary, and a conclusion that merely repeats the thesis. Before answering, list any claim that needs a source but is unsupported by my material. Then check that every section gives the target reader a new idea, decision rule, or action. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [TARGET READER] | Describe the specific audience, their context, and the problem they are trying to solve. | First-time managers at 50–300 person software companies who have trouble making one-on-ones useful |
| [TARGET KEYWORD OR QUESTION] | Enter the search phrase or concrete reader question the post should address. | how to run effective one-on-one meetings |
| [THESIS AND ANGLE] | State your main argument, perspective, or non-obvious conclusion. | A good one-on-one is not a status meeting; it is a recurring space for the employee’s priorities, judgment, and obstacles |
| [SOURCE MATERIAL] | Paste your notes, examples, evidence, source links, and any approved quotes. | My notes from managing six people: shared agenda, employee speaks first, 10-minute career discussion monthly, examples of questions that surfaced a blocked launch |
| [FORMAT AND LENGTH] | Specify the intended post style and approximate word count. | Practical essay, 1,200–1,500 words |
| [READER TAKEAWAY] | State what the reader should understand, decide, or do after reading. | A repeatable agenda and five questions they can use in their next one-on-one |
How to use
- Paste your reader, thesis, and source material before asking for a draft; the source notes determine what claims the post can make.
- Approve or revise the outline before using the full draft, especially the opening and section order.
- Fact-check every statistic, quote, and attributed claim against your notes or original sources before publishing.
- Follow up with: “Give me three alternate openings that begin with a concrete scene from the supplied notes, not a broad trend claim.”
Variations
Subscriber essay
Use when writing a personal, opinionated post for existing subscribers.
Outline and draft a [WORD COUNT]-word subscriber essay about [TOPIC] for [AUDIENCE]. My central observation is [OBSERVATION], supported by these real experiences and notes: [NOTES]. Use a reflective but precise voice. Structure it as an opening scene or moment, the argument it revealed, two or three implications for the reader, one honest caveat, and a closing question or action. Do not invent scenes, dialogue, outcomes, or lessons. Before drafting, flag any conclusion my notes cannot support and check that the post has a clear argument beyond personal storytelling.
Research brief
Use when readers need a sourced analysis rather than a personal essay.
Create a Substack research brief on [QUESTION] for [AUDIENCE] using only [SOURCES AND NOTES]. Produce a 150-word executive summary, a 1,000-word analysis with clear subheadings, a table of key findings and source links, and three implications. Separate facts, reported views, and my inference. Include dates for time-sensitive claims. Do not fill gaps with plausible data or unnamed experts. Before answering, flag unsupported claims and check that each implication follows from the evidence rather than from a headline.
Issue series plan
Use when one topic should become several connected Substack posts.
Plan a [NUMBER]-issue Substack series for [TARGET READER] about [SERIES TOPIC]. The reader’s core problem is [PROBLEM], and my available expertise and source material are [MATERIAL]. For each issue, provide a headline, search or subscriber intent, specific promise, 4-part outline, required evidence, and a bridge to the next issue. Avoid splitting one shallow article into several posts. Do not claim research or examples I have not supplied. Check that every issue stands alone while moving the reader toward [OUTCOME].
Tips
- Start from a reader decision or recurring problem, not a broad topic; “how to run one-on-ones” is more actionable than “management.”
- Put the thesis near the start, then earn it with examples, evidence, and a useful distinction rather than saving the point for the end.
- Use keywords as labels for reader intent, not as phrases to repeat; forced repetition makes a post less trustworthy.
- Keep a source list beside the draft and mark which lines are personal observation, reported fact, and inference before publication.
FAQ
Can AI write a Substack post from a keyword alone?
It can create an outline, but a useful and credible post needs your point of view and supporting material. Otherwise it tends to produce broad, interchangeable advice.
How often should I use the target keyword?
Use it where it helps a reader identify the subject: usually the headline, opening, and a relevant subheading. Do not force a frequency target.
Should I publish an AI draft without editing it?
No. Add your actual examples, verify every claim, and edit the structure and voice until it expresses a point only you can support.