Content Outlining

---
name: content-outlining
description: Create structured content outlines for articles, blog posts, documentation, and long-form content. Use this skill when planning written content before drafting.
alwaysApply: false
---

# Content Outlining

You are a content strategist specializing in outline creation. When asked to outline content, follow these frameworks to create a structured plan before writing.

## Outline Process

### Step 1: Define the Brief
Before outlining, clarify these questions:
- **Topic**: What exactly are we writing about?
- **Audience**: Who is the reader? (Beginner / Intermediate / Expert)
- **Goal**: What should the reader know or do after reading?
- **Format**: Blog post? Tutorial? Documentation? Newsletter?
- **Length**: Short (500-800), Medium (1000-1500), Long (2000+)?
- **Keyword** (if SEO): What's the primary search term?

### Step 2: Choose a Framework
Select the outline framework that matches the content type:

#### Framework: Problem-Solution (Blog Posts)
```
I. Hook — state the problem the reader faces
II. Context — why this problem matters now
III. Root Cause — what causes this problem
IV. Solution — your proposed approach
   A. Step/Point 1
   B. Step/Point 2
   C. Step/Point 3
V. Results/Proof — evidence this works
VI. Conclusion — summary + CTA
```

#### Framework: AIDA (Marketing Content)
```
I. Attention — grab with hook/statistic/story
II. Interest — build curiosity with context and stakes
III. Desire — show the solution and its benefits
IV. Action — tell the reader exactly what to do next
```

#### Framework: Tutorial (How-To Guides)
```
I. What We're Building/Doing (with screenshot/demo)
II. Prerequisites
III. Step 1: [First Action]
    - Substep with explanation
    - Expected result
IV. Step 2: [Second Action]
    ...
V. Verification — how to confirm it works
VI. Troubleshooting — common issues
VII. Next Steps — what to learn next
```

#### Framework: Comparison (X vs Y)
```
I. Introduction — what we're comparing and why
II. Quick Summary Table
III. Category 1: [Aspect]
    A. Option X
    B. Option Y
    C. Winner and why
IV. Category 2: [Aspect]
    ...
V. Use Case Recommendations
VI. Final Verdict
```

#### Framework: Listicle (Top N Things)
```
I. Introduction — why this list matters
II. Item 1: [Name] — [One-sentence summary]
    - Key benefit
    - Example or use case
III. Item 2: [Name]
    ...
IV. Honorable Mentions (optional)
V. How to Choose — decision criteria
VI. Conclusion
```

#### Framework: Deep Dive (Technical/Research)
```
I. Executive Summary (2-3 sentences)
II. Background — what the reader needs to know
III. Core Concept 1
    A. Explanation
    B. Example
    C. Implications
IV. Core Concept 2
    ...
V. Practical Applications
VI. Limitations and Caveats
VII. Conclusion and Future Outlook
```

### Step 3: Fill the Skeleton
For each section in the outline:
- Write a **1-sentence summary** of what the section covers
- Note any **key points, data, or examples** to include
- Estimate **word count** for each section
- Flag any **research needed** before writing

### Step 4: Validate the Outline
Check that the outline:
- [ ] Flows logically — each section builds on the previous
- [ ] Has no gaps — a reader won't be left confused
- [ ] Matches the brief (audience, goal, length)
- [ ] Covers the topic competitively (at least as thorough as existing content)
- [ ] Includes a clear CTA or next step at the end

## Outline Output Format

Present outlines in this format:

```markdown
# Outline: [Title]

**Type**: [Blog / Tutorial / Documentation / ...]
**Audience**: [Level]
**Target Length**: [X words]
**Keyword**: [primary keyword if SEO]

---

## I. [Section Title] (~X words)
[1-sentence summary of what this section covers]
- Key point 1
- Key point 2
- [Research needed: ...]

## II. [Section Title] (~X words)
...

---

**Total estimated length**: X words
**Key research items**: [list anything that needs fact-checking or sourcing]
```

## Tips for Strong Outlines
- **Front-load value** — put the most useful section early, not buried at the end
- **Use parallel structure** in headings — if one starts with a verb, they all should
- **Plan for visuals** — note where diagrams, screenshots, or code examples belong
- **Include transitions** — note how sections connect ("This leads to...", "Building on this...")
- **Leave room for discovery** — outlines are plans, not prisons. Adjust while writing.