Article outline with a clear argument

Build a structured outline with a thesis, section goals and evidence to gather before you start drafting.

Change note: Initial version

Prompt

Create a detailed outline for an article.

Topic: {{topic}}
Format: {{format}}
Reader and what they already know: {{audience}}
The point I want to make: {{thesis}}
Target length: {{word_count}} words
What I already have (research, stories, data): {{material}}

Build the outline so that:
- It opens with a hook idea and states the thesis in a single sentence.
- Each section has a heading, a one-line purpose ("this section proves/explains..."), 2-4 bullet points and a suggested word count.
- The sections build logically: each one answers the question the previous one raises.
- It includes the strongest counterargument and where to answer it.
- It flags where I still need evidence, examples or an expert quote, using "NEEDS:" tags.
- It finishes with a conclusion that does more than summarise.

Output format: thesis line, then the outline in numbered sections, then a list of all NEEDS items ordered by priority. Ask me up to 3 questions first only if the thesis is unclear.

Variables

• {{topic}}Topictext

  Default: The hidden cost of constant meetings for remote teams

• {{format}}Formatselect

  Options: Long-form blog article, Opinion piece, How-to guide, Newsletter essay, Feature article, White paper

  Default: Long-form blog article

• {{audience}}Readertext

  Default: Remote team leads who already feel overloaded by calendar invites

• {{thesis}}Your pointtext

  Default: Most meeting overload is a documentation problem, not a scheduling problem

• {{word_count}}Word countnumber

  Default: 1500

• {{material}}Your materiallong

  Default: One story about cutting my team's meetings by 40%; a survey stat I half-remember; nothing else yet.

Example output

Thesis: Most meeting overload is a documentation problem, not a scheduling problem.

1. The hook: the calendar that eats a week (150 words)
Purpose: make the pain concrete.
- Open with the 40% cut story, starting from the before state.
- NEEDS: exact hours per week the team reclaimed.

2. Why we blame scheduling (200 words)
Purpose: explain the common fix and why it fails.
- Focus time blocks, no-meeting days.
- Why people still end up in meetings.

3. What meetings are really doing (300 words)
Purpose: prove the thesis.
- Meetings as a substitute for missing written context.
- Three kinds of meetings that disappear once something is documented.
- NEEDS: survey stat with source.

4. Counterargument: some talks must be live (200 words)
- Answer: separate decisions from updates.

5. How to start (400 words)
6. Conclusion (150 words)

NEEDS by priority: survey source; hours reclaimed; one outside expert quote.

Notes

The NEEDS tags turn the outline into a research to-do list. Paste the outline back after research and ask for a draft one section at a time.