module: "MODULE 2" category: "DIGITAL FTES: ENGINEERING" title: "Wrong List Type = Wrong Code. Here's the Rule." description: "Bullet points and numbered lists are not interchangeable. One tells AI items are independent. The other tells AI sequence is mandatory. Getting this wrong silently breaks your spec." cta_hook: "Ask one question before every list: does order matter?" warning_banner: "Using a bullet list for installation steps tells AI the steps are independent — it may generate them out of order. One wrong list type, one broken build." the_3_rules: title: "Bullets = Independent" description: "Unordered lists (-) signal that items have no required sequence. Use them for features, requirements, and options where order doesn't affect the outcome." fix: "Fix → Unordered Lists" title: "Numbers = Sequence" description: "Ordered lists (1. 2. 3.) are a contract of execution. Each step depends on the previous. AI treats them as mandatory sequence — not suggestions." fix: "Fix → Ordered Lists" title: "The Order Matters Test" description: "Before writing any list, ask: if I shuffled these items, would it break? Yes → numbered list. No → bullet list. This single test eliminates all list-type errors." fix: "Fix → Order Matters Test" what_this_fixes: flow: step1: "Random List Usage" step2: "Order Matters Test" step3: "Correct List Type" result: "Dependency-Aware AI" quote: "A numbered list is not just formatting — it is a contract of execution. AI reads it as: step 1 before step 2, no exceptions." short_hook: "Does order matter? Answer that first."

Mapping Dependencies with Lists and Sequential Logic

Headings provide the skeleton, but lists provide the specific, actionable requirements. This lesson teaches you how to map dependencies and workflows using unordered and ordered lists. You will learn the "Order Matters Test" to decide between independent features (bullets) and sequential instructions (numbered steps), ensuring that your AI implementation partner understands exactly what to build—and in what specific order—to achieve a successful outcome.

---

Concept 1: Unordered Lists (Bullet Points)

Use unordered lists when you have items that don't need to be in any specific order. In markdown, create them with a dash (-) or asterisk (*) followed by a space.

Basic Syntax

Nested Lists

You can create sub-items by indenting with 2 or 4 spaces:

[!NOTE] Some markdown parsers require a blank line before lists to render correctly. If your list isn't rendering, add a blank line above it.

---

Concept 2: Ordered Lists (Numbered Steps)

Use ordered lists when items must be done in a specific sequence. In markdown, create them by typing 1. followed by a space.

Basic Syntax

[!TIP] Markdown auto-numbers based on the first number in the list. However, for AI agents reading the raw source, it is best practice to use correct sequential numbers (1., 2., 3.).

When to Use Ordered Lists

Use numbered lists when:

• Steps must be done in sequence
• You're showing installation steps or processes
• Each step depends on the previous one

---

Concept 3: Choosing the Right List Type

Ask yourself: Does order matter?

• Use unordered lists (-) for features, requirements, or alternatives where items are independent.
• Use ordered lists (1.) for installation, workflows, or troubleshooting where sequence affects the outcome.

Side-by-Side Example

Unordered (Features):

• Dark mode support
• Export to PDF
• Auto-save

Ordered (Setup):

1. Create account
2. Verify email address
3. Set up profile

---

Practice Exercise: Task Tracker App (Part 2 - Lists)

Open your Task Tracker App specification from Lesson 2. You'll now add lists to organize features and installation.

Your Task for Lesson 3

Part 1: Add Feature Descriptions Under each Level 3 heading in the Features section, add bullet points:

Part 2: Add Installation Steps Fill in the Installation section with numbered steps:

---

Try With AI

Prompt 1: List Type Check

Prompt 2: Clarity Check

Prompt 3: Improvement Suggestion