---
name: draft
description: Expand an outline into a full article draft
argument-hint: "[outline-file]"
---

# Draft Skill

Expand a structured outline into a complete article draft, following Ahrefs-style content guidelines.

**Important**: This skill uses section-by-section drafting to ensure consistent quality throughout. Each H2 section is written independently with minimal context, preventing quality degradation in later sections.

## Input

**Outline file path** - Path to the outline file (from `/outline` skill)

**Optional: `--references`** - Comma-separated list of URLs, file paths, image paths, or pasted content

---

## Style Reference

Before drafting, read `./reference/style-reference.md` to calibrate voice and tone.

---

## Core Writing Principles

1. **Specific examples for every point** - Never make a claim without illustrating it
2. **First-person experiences** - Use "I" and "We", include anecdotes
3. **Include opinions** - Take a stance, don't be wishy-washy
4. **Be detailed and exhaustive** - Cover topics thoroughly
5. **MECE structure** - Mutually exclusive sections, collectively exhaustive coverage
6. **BLUF principle** - Bottom Line Up Front, state the key point immediately
7. **Humor and personality** - Be human, not robotic
8. **Avoid exaggerated language** - No "mastery of data", "revolutionary", "game-changing"
9. **Reference Ahrefs naturally** - Mention relevant tools/features when they genuinely help

---

## Style Guidelines

### Voice and Tone
- Write in **first person** (I/We)
- Use **American English** (optimize, not optimise)
- **Casual tone** - Start sentences with "But..." or "So..." when it flows naturally
- **No swearing** or questionable language
- Be direct, not formal

### Sentence and Paragraph Structure
- **One thought per sentence**
- **Max 3 lines per paragraph**
- **Avoid fluff** - Cut throat-clearing phrases
- **Simple language**

### Length
- Target: **1,000-3,000 words** (based on outline word count targets)
- **As short as possible** - Educate simply, don't pad for word count

### Subheadings
- **Sentence case** ("What is bounce rate?" not "What Is Bounce Rate?")
- **One point per heading**
- **Under 15 words**
- **Never place subheadings back-to-back** - Add intro text between heading and subheading

---

## Content Structure

### Introduction (Under 100 words)

Use the **PAS formula**: Problem → Agitate → Solution

### Body Sections

Use the **inverted pyramid** for each section:
1. **Need to know** first (the essential point)
2. **Nice to know** second (supporting details, context)

When writing definitions: `[Term] [conjunction] [definition in 1-3 sentences]`

When writing explanations: Always explain **what** AND **why**

When using examples: Be specific (real numbers, real sites, personal experience)

When a screenshot would help: `[SCREENSHOT: Description of what to show]`

---

## Workflow: Section-by-Section Drafting

### Phase 0: User Reference Review (if `--references` provided)

Extract a **Reference Card**:
1. POV and angles
2. First-person examples
3. Specific data and named entities
4. Unique framing

### Phase 0.5: Style Calibration

Read `./reference/style-reference.md` and extract a **Style Card** (~200 words):
1. Voice markers (3 examples)
2. BLUF examples (2 examples)
3. Transition patterns (2 examples)
4. Specificity markers (2 examples)
5. Anecdote structure (1 example)

### Phase 1: Setup

Read the outline, extract article metadata, create the draft file.

### Phase 2: Section-by-Section Drafting

For each H2 section:
1. **Ground in reference**: Quote ONE passage from the style reference relevant to this section type
2. **Load context**: Style Card, article metadata, this section's outline, previous section's last paragraph, next section's header
3. **Write the complete section** matching the voice and patterns
4. **Append the completed section** to the draft file
5. **Move to the next section**

### Phase 3: Introduction & Conclusion

Write introduction AFTER body sections (use PAS formula, under 100 words).
Write conclusion LAST (synthesize full article, include "Final thoughts" and Twitter CTA, under 150 words).

### Phase 4: Assembly Review

Read complete draft, check transitions, verify consistency, update metadata.

---

## Per-Section Quality Requirements

Each section MUST include:
- [ ] BLUF in first 1-2 sentences
- [ ] At least one specific example (number, name, or personal experience)
- [ ] First-person voice
- [ ] Connection to article thesis or previous section
- [ ] No paragraphs over 3 lines

---

## Output

Save to `./4-drafts/[keyword-slug].md` with full article content plus Draft Notes (screenshots needed, illustrations needed, fact-check list, questions for review).

## Example Usage

```
/draft ./3-outlines-annotated/pinterest-seo.md
```