Step 5: Introduction Writing

Goal

Write the introduction that sets the stage for the entire guide. This is often the most important part - it determines whether readers continue or stop.

---

Inputs Required

| Input | Source | Purpose | |-------|--------|---------| | Revised syllabus | syllabus_revised.md | What guide covers | | Document spec | document_spec.md | Style/tone requirements | | Topic analyses | topic_analysis/*.md | Key themes and hooks | | Interview Q&A | otazky.md | Personal story elements |

---

Introduction Components

A strong introduction has these elements:

1. Hook (grab attention)
2. Problem statement (why this matters)
3. Credibility (why listen to you)
4. Promise (what reader will learn)
5. Roadmap (how guide is structured)
6. How to use this guide

---

Process

5.1 Hook Development

The first paragraph determines if reader continues.

Hook Types:

1. Story hook: Start with a personal anecdote
2. Problem hook: State a pain point reader recognizes
3. Statistic hook: Start with surprising data
4. Question hook: Ask a question reader wants answered
5. Quote hook: Start with powerful quote

Brainstorm 3-5 potential hooks:

## Hook Options

### Option A: Story
"Last year, I spent an hour arguing with ChatGPT about a simple bug fix.
The AI kept suggesting solutions that wouldn't work, I kept rejecting them,
and we both got frustrated. Then I realized: the problem wasn't the AI.
It was me."

### Option B: Problem
"Most people who try AI tools give up within a month. Not because AI doesn't work,
but because they're using it wrong. They prompt. They should provide context."

### Option C: Statistic
"According to recent research, AI performance actually decreases as you give it
more information. More isn't better. The right information is better."

### Option D: Question
"What's the difference between a senior developer and a junior one?
Same skills, same tools, same education. The difference is context."

### Option E: Quote
"'Context engineering is the delicate art and science of filling the context window
with just the right information.' — Andrej Karpathy, co-founder of OpenAI"

Selection criteria:

• Does it create curiosity?
• Is it relatable to target audience?
• Does it connect to the guide's main theme?
• Is it authentic to your voice?

---

5.2 Problem Statement

After the hook, crystallize the problem:

## Problem Statement Draft

**The surface problem:**
AI outputs are inconsistent, often unusable, requiring multiple iterations.

**The real problem:**
Users focus on crafting the perfect prompt while ignoring context -
the information AI actually needs to help them.

**The cost of the problem:**
- Wasted time on iterations
- Frustration leading to AI abandonment
- Missed productivity gains
- Competitive disadvantage

**Why it persists:**
- "Prompt engineering" term misleads people
- No systematic approach taught
- Trial and error is slow teacher

---

5.3 Credibility Section

Why should readers trust you?

## Credibility Elements

### Experience
- 20+ years in software development
- Daily AI user for [X] years
- Team lead/technical role

### Proof Points
- Specific results achieved
- Examples of transformation
- Recognition (if any)

### Honesty Element
"I made all these mistakes myself. This guide comes from learning the hard way."

### External Validation
- Karpathy endorsing concept
- Industry leaders using term
- Research backing claims

**Draft paragraph:**
"I've been programming for over 20 years. When AI coding assistants appeared,
I jumped in like everyone else - and failed like everyone else. I gave AI massive
tasks, provided minimal context, and blamed the tool when results were poor.
This guide is what I wish existed when I started."

---

5.4 Promise/Value Proposition

What will reader gain?

## Promise Statement

### Primary Promise
"By the end of this guide, you'll know how to get consistent, useful output
from any AI tool - every time."

### Specific Outcomes
After reading, you will:
- Understand why your AI prompts fail
- Know the 5 components of effective context
- Have templates you can use immediately
- Recognize when to iterate vs. start fresh
- Apply these principles to any AI tool

### Anti-promises (what this isn't)
- This is NOT a prompt library to copy-paste
- This is NOT tool-specific (works with any AI)
- This is NOT about tricking AI into better responses

**Draft paragraph:**
"This guide won't give you magic prompts to copy-paste. Instead, it will change
how you think about AI interaction. You'll learn the principles that make
AI work for you - principles that apply whether you're using ChatGPT, Claude,
Gemini, or whatever comes next."

---

5.5 Roadmap

Show the structure:

## Roadmap Draft

"This guide is organized into [X] parts:

**Part 1: Foundations** explains what context engineering is and why it matters.
Start here if you're new to the concept.

**Part 2: The Practice** shows you exactly how to do it - with templates,
examples, and common mistakes to avoid.

**Part 3: Beyond Basics** covers team implementation, tool selection,
and where this field is heading.

**Appendix** includes quick reference materials you'll return to often.

Each chapter builds on the previous, but chapters can also stand alone
if you want to jump to a specific topic."

---

5.6 How to Use This Guide

Help readers navigate:

## How to Use This Guide

**If you're completely new to AI:**
Read Part 1 first. Don't skip to the practical chapters -
the foundation matters.

**If you're already using AI but frustrated:**
Skim Chapter 1, then focus on Chapters 3-5.
The quick reference in the Appendix is your friend.

**If you're implementing AI for a team:**
Start with Chapter [X] on team implementation,
then read backwards for the principles.

**For everyone:**
- Keep the Appendix handy while working
- Try examples from each chapter before moving on
- Come back to sections as you encounter specific challenges

---

Introduction Template

# Introduction

[HOOK - 2-3 sentences that grab attention]

[PROBLEM - 2-3 paragraphs explaining the problem this guide solves]

[CREDIBILITY - 1-2 paragraphs on why you're qualified to write this]

[PROMISE - What reader will learn/gain, specific outcomes]

[ROADMAP - Brief overview of guide structure]

[HOW TO USE - Guidance for different reader types]

---

Let's begin.

---

Writing Process

Step 1: Draft Hook Options (15 min)

Write 3-5 different hooks. Don't edit, just write.

Step 2: Select Best Hook (5 min)

Pick the one that's most authentic and compelling.

Step 3: Draft Body (30-45 min)

Write through each section. Don't perfect - get it down.

Step 4: First Edit (15 min)

Trim fluff, strengthen weak sentences, check flow.

Step 5: Read Aloud (10 min)

Literally read aloud. Awkward phrases become obvious.

Step 6: Final Polish (10 min)

Final adjustments, ensure it matches document spec.

---

Quality Criteria

| Criterion | Check | |-----------|-------| | Hook captures attention in first sentence | ☐ | | Problem is clearly stated | ☐ | | Credibility established without bragging | ☐ | | Promise is specific and achievable | ☐ | | Roadmap helps reader navigate | ☐ | | Tone matches document spec | ☐ | | Length appropriate (500-800 words) | ☐ | | Ends with energy, not whimper | ☐ |

---

Common Pitfalls

1. Burying the lead - Don't warm up for two paragraphs. Start strong.
2. Over-promising - Don't claim "master AI in 10 minutes"
3. False modesty - Don't undermine your credibility
4. Too long - Introduction shouldn't be a chapter
5. No roadmap - Reader should know what's coming
6. Generic opening - "AI is changing the world" = immediate skip

---

Example: Good vs Bad Introduction

Bad:

"Artificial Intelligence has become increasingly prevalent in our modern society. Many people are now using AI tools for various tasks. However, not everyone knows how to use them effectively. In this guide, we will explore different aspects of AI usage and how to improve your results..."

Problem: Generic, boring, no personality, passive voice, no hook.

Good:

"Last month, I watched a senior developer spend three hours fighting with Claude about a database migration. The AI kept suggesting the same wrong approach. Frustrated, he gave up and wrote it manually.

The next day, I asked Claude the same question. I got a working solution in four minutes. Same AI. Same problem. Different result.

The difference wasn't intelligence or experience. It was context. He told the AI what to do. I told it what to do, why, what constraints existed, and what success looked like.

This guide is about that difference..."

Better: Story hook, demonstrates the problem, shows credibility subtly, makes reader curious.

---

Output

Create file: guide_draft/00_introduction.md

---

Time Estimate

• Hook brainstorming: 15-20 minutes
• Body drafting: 30-45 minutes
• Editing: 25-35 minutes

Total: 1-1.5 hours

---

Next Step

→ Once introduction is complete, proceed to 06_chapter_writing.md