DEV Community: Dario Radečić

The 1/3/2/1 Introduction Prompt: Craft Attention-Grabbing Introductions in Seconds

Dario Radečić — Sun, 27 Jul 2025 18:05:30 +0000

Writing introductions shouldn't take longer than writing the entire article body.

You know your topic inside and out, but crafting that opener feels impossible. Most technical writers spend 30-60 minutes on introductions alone, cycling through approaches that sound too formal, too casual, or miss the mark entirely. You end up with generic openings that don't grab attention or abandon articles because you can't get past paragraph one.

A simple AI prompt solves this in under a minute. The 1/3/2/1 structure gives you a proven framework, and when you feed it to Claude or ChatGPT, you get introductions that hook readers immediately.

This guide shows you the exact prompt, how to use it, and real examples of introduction writing automation.

Subscribe to Writing for Developers — The leading newsletter helping developers automate content creation with curated prompts that turn ChatGPT & Claude into your own Technical Content Writing Assistant.

The 1/3/2/1 Introduction Format Explained

I already covered the theory behind 1/3/2/1 introductions, so I won't repeat myself here:

The 1/3/2/1 Format: The Only Formula You Need for Attention-Grabbing Introductions

The Introduction Hook Formula for technical articles + AI prompt to automate it

writingfordevs.substack.com

If you don't have time to read that piece, here's what you need to know:

The 1/3/2/1 format creates seven-sentence introductions across four paragraphs
Each number tells you how many sentences go in each paragraph
This structure gives readers just enough information to know if you're solving their specific problem

Here's what each sentence does:

The first sentence is your bold opener - hit the pain point without hesitation.

The second sentence clarifies your bold opener with more context. The third sentence adds credibility by including exact numbers or a real-world example. The fourth sentence rounds out your argument and guides the reader toward your solution.

The fifth sentence introduces and explains your solution clearly. The sixth sentence expands on why your solution works and why you're confident in it.

The seventh sentence tells readers what comes next in the article.

Read the original article to understand why this format works so well for technical content.

Now let me show you the prompt.

The 1/3/2/1 Introduction Prompt

Here's the prompt you can use with ChatGPT, Claude, or any other LLM to craft attention-grabbing introductions in seconds:

Grab my 1/3/2/1 Introduction Prompt by reading the article on Substack.

The 1/3/2/1 Introduction Prompt: Craft Attention-Grabbing Introductions in Seconds

This AI prompt turns any topic into a structured introduction that hooks readers instantly

writingfordevs.substack.com

The 1/3/2/1 Introduction Format: The Only Formula You Need for Attention-Grabbing Introductions

Dario Radečić — Sun, 27 Jul 2025 18:02:24 +0000

Staring at a blank page for 30 minutes every time you start writing an article?

Technical writing introductions are tricky because you need to hook the reader immediately while being helpful and proving your article is the only one they need. Most writers get stuck trying to balance being engaging with being informative, and often rewrite the same opening paragraph multiple times. The result? You waste precious time that could be spent on the actual content, and you might even end up with a weak opener that doesn't grab attention.

The 1/3/2/1 format solves this problem by giving you a proven structure to follow every time. This seven-sentence framework takes the guesswork out of introductions and ensures you hit all the right notes - from addressing pain points to introducing your solution.

Here's how to use the 1/3/2/1 format to write compelling introductions that hook readers and keep them reading until the end.

What Is 1/3/2/1 Article Introduction Format

I was first introduced to the 1/3/2/1 format in the book The Art and Business of Online Writing by Nicolas Cole. To say it trasnformed the way I write would be an understatement.

However, the book focuses on writing in general, so some advice doesn't fully translate to technical writing. That's why you're here.

The 1/3/2/1 format is a seven-sentence introduction structure that breaks down into four paragraphs. Each number tells you how many sentences to write in each paragraph - one sentence, then three sentences, then two sentences, then one final sentence.

This format gives readers just enough information to know if you're solving their specific problem. You won't overwhelm them with a long introduction and make them scroll away, and you won't leave them confused about what they're getting either.

The beauty of this structure lies in its predictability.

You can express any idea in seven sentences, no matter how complex the topic might be. It works best for technical pieces and how-to guides. Opinion pieces and listicles need a slightly different approach.

It has concrete benefits for the writer, too.

You'll never stare at a blank page wondering how to start because you have a clear roadmap. Write one hook sentence, expand on the problem with three sentences, present your solution in two sentences, then transition to your main content with one final sentence.

And you're done.

Why 1/3/2/1 Works Wonders for Technical Articles and How-to Guides

The 1/3/2/1 structure hits the sweet spot for technical articles.

Anything shorter like 1/3/1 doesn't give you enough space to address the pain point and provide a solution overview. It might work for opinion pieces or listicles where you want to get to the meat immediately, but technical content needs more setup.

Anything longer than 1/3/2/1 makes readers abandon your article before they reach the good stuff. Seven sentences is the maximum most people will read before deciding if your content is worth their time.

This format addresses four elements that technical readers need:

It identifies their specific pain point
It builds on the pain point so readers know you understand their problem
It shows you have a real solution
It tells them exactly what they'll learn next so they can decide if it's worth continuing

The structure forces you to be concrete rather than vague. You can't waste sentences on fluff when you only have seven to work with.

1/3/2/1 Format Explained

Here's exactly how to structure each paragraph and sentence in your introduction.

What each paragraph does

The first paragraph contains one bold sentence that addresses the reader's pain point directly. Hit them where it hurts most.

The second paragraph has three sentences that build on the pain point. Make the reader feel like you've been in their shoes, struggling with the exact problem.

The third paragraph has two sentences that introduce your solution and explain why they should care about it. This is where you transition from problem to solution.

The fourth paragraph has one sentence that bridges your introduction to the article body. Tell them what they'll learn next.

What each sentence does

The first sentence is your bold opener - hit the pain point without hesitation.

The second sentence clarifies your bold opener with more context. The third sentence adds credibility by including exact numbers or a real-world example. The fourth sentence rounds out your argument and guides the reader toward your solution.

The fifth sentence introduces and explains your solution clearly. The sixth sentence expands on why your solution works and why you're confident in it.

The seventh sentence tells readers what comes next in the article.

A Real-World Example of the 1/3/2/1 Structure

Here's the best part - this article's introduction uses the 1/3/2/1 structure.

I didn't write it from scratch though. I used my ChatGPT and Claude prompt called The 1/3/2/1 Introduction Prompt to generate the introduction, then made minor tweaks. The whole process took under two minutes.

For reference, here's what Claude Sonnet 4 produced:

I made a couple of small edits (left = before, right = after):

Compare that to my usual routine - spending 30+ minutes crafting introductions, with most of that time wasted on the opening sentence alone - it's a huge time and energy saver.

Next Steps

Your next order of business is to put the 1/3/2/1 structure to work.

Start by practicing the format manually with your current writing projects. Count your sentences and make sure you hit each part: one bold opener, three pain point sentences, two solution sentences, and one transition. This hands-on practice helps you internalize the structure.

Once you're comfortable with the format, use AI to automate the writing process with my The 1/3/2/1 Introduction Prompt.

Talk soon,

Dario Radecic

From Keyword to Tech Article Outline: This AI Prompt Kills Writer's Block

Dario Radečić — Sun, 27 Jul 2025 17:57:45 +0000

Staring at a blank document when you have a great article idea is the worst part of technical writing.

You know what you want to write about, but turning that single topic into a structured outline feels overwhelming. Most writers waste hours trying to figure out what sections to include, what order makes sense, and whether they're missing important points. The result? You either end up with a messy outline that doesn't flow, or you procrastinate and ditch the idea entirely.

AI can solve this problem in under a minute. Instead of struggling with structure, you give AI a topic and it analyzes top-performing articles on Google to see what works.

The result is a 90% ready outline in Markdown format. You just add your personal touch and start writing.

This article shows you the exact prompt that transforms any topic into a complete article outline.

Let's dive in.

Why Manual Outline Creation Wastes Your Time

Hours.

That's how long most writers spend figuring out article structure before they write a single word. You have a topic in your head, but the moment you open a blank document, everything falls apart.

Your brain jumps between different angles. Should you start with the basics or dive straight into advanced concepts? What examples should you include? Before you know it, you've spent an hour thinking about structure without writing a single word.

You don't need to figure this out from scratch. Thousands of articles already exist on your topic. The best ones follow proven patterns, and an LLM with internet access can analyze them for you.

This prompt fixes that. It helps you:

Skip the guesswork by analyzing what actually works in your niche
Get a research-backed structure in under a minute
Focus your energy on writing instead of planning
Build on patterns from top-ranking articles in your field

Let me show you the prompt next.

The Article Outline Researcher and Writer Prompt

Here's the prompt you can use with ChatGPT, Claude, or any other LLM that has a web search capability:

You are a professional tech writer. Your task is to analyze a topic submitted by the user and create an article outline that includes:
- A working article title
- A full markdown outline with:
  - H2 sections
  - H3 subsections under each H2 (if needed)
  - Bullet points for each subsection explaining what will be covered

Each bullet point must describe a concept, insight, technique, or example that should be addressed. The outline must be complete enough to guide a writer through drafting the article without missing key points.

### Target audience
Tech professionals, software developers, data scientists, and other experienced IT practitioners.

### Research instructions
- Use the top 5 Google search results for the topic (or closely related terms)
- Only include blog posts and articles from reputable publications
- Exclude Reddit, Stack Overflow, forums, and Q&A sites

For each selected article:
- Extract the title, H2/H3 headings
- Analyze the content under each heading
- Derive relevant bullet points from the content (not just the heading text)
- Look for tone, structure, patterns, and scope

### Writing style
- Write in American English
- Use conversational and simple to understand language - most readers aren't native English speakers
- Use title casing for H2 headings (This is the Title Casing)
- Use sentence case for H3 headings (This is the sentence casing)
- Always use contractions (e.g., “don’t” instead of “do not”) to keep the tone natural.
- Avoid fluff words and filler content - the article is already dense and packed with technical jargon

### Output format (Markdown)
Return the article outline in this exact structure:
~
# [Working Article Title]
- [Intro: what the article will cover]
- [Intro: target audience context]
- [Intro: article value proposition]
## [H2 Section Title]
[One sentence describing this section’s purpose]
### [H3 Subsection Title]
- [Topic or concept to explain]
- [Key insight or point to emphasize]
- [Example or case study to reference]
### [H3 Subsection Title]
- ...
## [Another H2 Section Title]
[One sentence describing this section’s purpose]
### [H3 Subsection Title]
- ...
[Continue pattern for all sections...]
## Conclusion
- [Key takeaway to reinforce]
- [Next steps or action items]
~

The article should aim to be comprehensive and self-contained. Don’t rush or skip important topics. Include as many H2/H3 sections as needed to make it a complete resource, but avoid unnecessary sections—be economical and purposeful in your structure. Keep in mind that the final article should have 2000-5000 words, so keep the outline at a level that can contain that much content - don't exceed it.

### Final instruction
Now, ask the user to submit a topic (and any optional context or requirements). Do not ask them for anything else.

Testing the Prompt

Let's see how it works in practice.

Say you want to write an article comparing alternatives to Python's pandas library. Copy the prompt above and paste it into your LLM:

Once it asks for your input, explain your topic and add any optional context:

The AI takes about 30 seconds to perform web search and research. This isn't deep research - I tried that approach initially, but it kept ignoring my instructions and writing research documents instead of outlines. Useful, but not what we need.

The AI will present you with a Markdown article outline:

Copy this outline into a new Markdown document for refinement. AI delivers a 90% ready structure, but the final 10% is what makes it yours. Add your personal insights, adjust sections based on your experience, and include examples that show your expertise.

Done.

Talk soon,

Dario Radecic

3 Reasons Why Every Tech Professional Should Start Writing Online Right Now

Dario Radečić — Sun, 27 Jul 2025 17:53:09 +0000

Tech professionals are getting hammered right now.

Layoffs hit every week. Pay cuts are the new normal. Headcount drops but the work doesn't. A single income stream was risky before - now it's just reckless.

There's only so much you can do at your 9 to 5. You need additional levers. A different approach. An option that boosts your income and gives you freedom to work from anywhere at any time.

Writing online did that for me. It can do the same for you.

AI makes writing online easier than ever for tech professionals. After writing 700+ articles, 80% of them before ChatGPT, I can tell you what used to take days now takes hours. Your unique perspective remains yours - AI just helps you express it faster.

Let me break down exactly why writing online works so well for tech professionals.

1. Writing Online Reinforces and Accelerates Your Learning

Want to learn something by heart? Teach it.

Writing online forces you to break down complex topics into simple language. No jargon. No hiding behind fancy terms. Just clear explanations communicated as simply as possible.

Here's the test: You think you understand Redis Queues after studying them for a week? Try explaining them to someone who's never heard the term. Think about what made it click for you originally and which parts of the documentation confused you most. Suddenly it's not so simple.

Teaching exposes the gaps in your understanding that you didn't even know existed.

When you can explain complex concepts in plain English, you prove you're not just technically skilled but also a clear communicator. That combination is rare and valuable.

In short:

If you think you understand a complex tech topic, write a how-to guide. It will expose any gaps in your understanding.
Explaining complex topics in plain English develops communication skills that set you apart in the AI era.

2. Writing Online Positions You as an Authority

Who comes to mind when you think about Apache Airflow? If your answer is Mark Lamberti, you're not alone. He's the perfect example of what it means to be an authority in a competitive niche.

Truth be told, this could be you.

Investing years writing quality materials on a single topic that resonate with readers has no other possible outcome than you becoming an authority in that niche. It's that simple - you just have to start and not give up when going gets hard or the initial excitement wears off.

This small action repeated over months and years unlocks the outcome you always wanted.

Here's what happens when you become the authority: Recruiters start reaching out to you instead of the other way around. You get invited to speak at conferences, consult on projects, and advise companies looking to optimize their content strategy. Companies create positions specifically for you.

In short:

Pick a tech topic you have experience in. Write better content about it for longer than anyone else. Own the niche.
Then watch the magic happen.

3. Writing Online Builds Multiple Income Streams

Tech layoffs aren't slowing down. Microsoft, Google, Amazon - they all cut thousands of jobs in 2024 and 2025. Small startups are even worse. They disappear overnight.

Your salary isn't safe. Neither is mine. Relying on one income stream is risky business in today's market.

Writing online creates multiple revenue streams that grow over time. Freelance articles pay $300-2000 each. Consulting gigs can bring in $5000+ per project. Technical writing contracts offer steady monthly income. You get the point.

I've been writing since 2020 while working full-time as a data scientist. What started as a side project now brings stable income monthly. The writing work keeps flowing even when tech hiring slows down. Different markets, different demand cycles.

You're building two careers at once. One protects you if the other fails.

In short:

Tech jobs aren't secure anymore. Writing online creates backup income streams that can grow into full-time revenue.
You get offers for both technical roles and writing positions. Double the opportunities, double the security.

Talk soon,

Dario Radecic