Write Command

Use this command to create comprehensive, SEO-optimized long-form blog content.

Usage

/write [topic or research brief]

What This Command Does

1. Creates complete, well-structured long-form articles (2000-3000+ words)
2. Optimizes content for target keywords and SEO best practices
3. Maintains your brand voice and messaging throughout
4. Integrates internal and external links strategically
5. Includes all meta elements for publishing

Process

Pre-Writing Review

• Research Brief: Review research brief from /research command if available
• Brand Voice: Check @context/brand-voice.md for tone and messaging
• Writing Examples: Study @context/writing-examples.md for style consistency
• Style Guide: Follow formatting rules from @context/style-guide.md
• SEO Guidelines: Apply requirements from @context/seo-guidelines.md
• Target Keywords: Integrate keywords from @context/target-keywords.md naturally

Content Structure

#### 1. Headline (H1)

• Include primary keyword naturally
• Create compelling, click-worthy title
• Keep under 60 characters for SERP display
• Promise clear value to reader

#### 2. Introduction (150-250 words)

CRITICAL: Direct Answer First (AI Search Optimization)

For any "best/top/how" query, the first 1-2 sentences MUST directly answer the question. AI scrapers (ChatGPT, Perplexity, Gemini) pull from the top of the page. Don't bury the answer behind narrative.

Example — "best project management tools":

The best project management tools in 2026 are Asana, Monday, and ClickUp — each built for different team sizes and workflows. Here's how they compare.

After the direct answer, use a hook to keep human readers engaged.

Choose ONE hook type for each article:

After the hook, follow the APP Formula:

• Agree: Acknowledge something the reader already believes/feels
• Promise: Tell them exactly what they'll learn or gain
• Preview: Brief overview of what's coming (can include mini table of contents for long posts)

• Keyword: Include primary keyword in first 100 words
• Credibility: Establish why you/this article is authoritative

#### 3. Key Takeaways Block (After Introduction)

REQUIRED: TL;DR block immediately after the introduction, before the first H2 body section.

This gets pulled into AI-generated summaries and helps both AI and human readers quickly assess the article's value.

> **Key Takeaways**
> - [Core finding or recommendation #1]
> - [Core finding or recommendation #2]
> - [Core finding or recommendation #3]
> - [Core finding or recommendation #4 if needed]
> - [Core finding or recommendation #5 if needed]

Rules:

• 3-5 bullet points
• Each bullet is a standalone claim with specifics (numbers, names, outcomes)
• NOT a table of contents — these are the article's actual conclusions
• Written after the full article is drafted (so the takeaways are accurate)

#### 4. Main Body (1800-2500+ words)

• Logical Flow: Organize sections in clear, progressive order
• H2 Sections: 4-7 main sections covering comprehensive topic scope
• H3 Subsections: Break complex sections into digestible pieces
• Keyword Integration: Use primary keyword 1-2% density, variations throughout
• Depth: Provide thorough, actionable information at each point
• Data: Reference statistics and studies to support claims
• Visuals: Note where images, screenshots, or graphics enhance understanding
• YouTube Embed: Include at least one relevant YouTube video (prefer your own channel, then authoritative third-party) — AI models cross-reference video and article content
• Lists: Use bulleted or numbered lists for scannability
• Formatting: Bold key concepts, use short paragraphs (2-4 sentences MAX)

REQUIRED: Mini-Stories (2-3 per article)

Research shows we're 22x more likely to remember facts wrapped in stories. Every article MUST include 2-3 mini-scenarios with:

• A specific person (use names, even if fictional: "Sarah," "Mike," "The team at Acme Corp")
• A concrete situation with details (dates, numbers, specifics)
• A clear outcome that illustrates the point

**Ex