module: "MODULE 2" category: "DIGITAL FTES: ENGINEERING" title: "AI Can't Read a Wall of Text — Give It a Blueprint" description: "Headings are not formatting. They are the skeleton of your specification — the mental map AI uses to navigate, prioritize, and execute your requirements." cta_hook: "Build the structure first. The content follows." warning_banner: "Skipping heading levels (H1 → H3) breaks document hierarchy for both humans and AI agents — requirements lose their parent context and generate misaligned code." the_3_rules: title: "One H1, Always" description: "The H1 heading is the document title — use it once. Everything else organizes beneath it. This gives AI a single entry point to understand the spec's purpose." fix: "Fix → Document Title" title: "Never Skip Levels" description: "H1 → H3 without H2 creates orphaned subsections. AI cannot determine what parent section a requirement belongs to — causing misaligned implementation." fix: "Fix → Sequential Hierarchy" title: "Headings Are Anchors" description: "AI uses headings as navigation landmarks. Content under ## Features is scoped to features. Content under ## Installation is scoped to setup. Headings define the context of everything beneath them." fix: "Fix → Structural Scope"

what_this_fixes:

• "Ends the 'wall of text' problem — AI gets a mental map of your document before reading a single requirement."
• "Eliminates misaligned code generation — requirements stay anchored to their correct section and context."
• "Builds your specification skeleton first — so you think in structure before you think in content."

flow: step1: "Wall of Text" step2: "Heading Hierarchy" step3: "Structural Blueprint" result: "Zero Context Drift"

quote: "When you write headings, you aren't organizing text — you are building the decision tree your AI agent navigates to implement your vision." short_hook: "Structure first. Content follows."

Architecting Information with Heading Hierarchies

In Lesson 1, you saw how structured text helps AI understand your intent. Now you'll learn the first building block of that structure: headings.

Imagine trying to find information in a document that's just one long wall of text. You'd scroll endlessly, hunting for the part you need. Now imagine that same document with clear sections: "Problem," "Solution," "Features," "Installation." Suddenly you can scan it in seconds.

In markdown, headings create this structure. They organize your document into sections that both humans and AI agents can quickly understand. When you write a specification, headings tell the AI: "This is the problem. These are the features. This is what the output should look like."

This lesson teaches you how to create clear document structure using headings.

---

Concept 1: Using Hash Symbols for Headings

Markdown uses the hash symbol (#) to create headings. More hash symbols = smaller heading.

• Level 1 (#): The document title (use once at the top)
• Level 2 (##): Main sections (Problem, Features, Installation, etc.)
• Level 3 (###): Subsections within a main section
• Level 4 (####): Deep technical details or exceptions

Example: A Simple Specification

Notice the pattern:

• One Level 1 heading for the title: # Task List App
• Four Level 2 headings for main sections: ## Problem, ## Features, and so on.

---

Concept 2: Following Proper Hierarchy

Headings must follow a logical hierarchy—you can't skip levels. You go from broad to specific.

Correct Hierarchy Example

Wrong Hierarchy Example (Don't Do This)

The fix: Always include Level 2 before Level 3.

---

Practice Exercise: Task Tracker App (Part 1 - Headings)

You'll build this same Task Tracker App specification across Lessons 2-5.

Your Task for Lesson 2

Create the structure for a Task Tracker App specification using only headings.

Template to fill in:

---

Try With AI

Prompt 1: Structure Check

Prompt 2: Clarity Check

Prompt 3: Organization Feedback