---
name: content-strategy
description: Plan and create content — blog posts, case studies, portfolio pieces. Triggers on "write blog post", "case study", "content plan", "content strategy", "portfolio content", "write article".
allowed-tools: Agent, Read, Glob, Grep, Write, Edit, WebSearch, WebFetch
---

# Content Strategy — Planning & Creation

Create high-quality content for agency self-promotion or client deliverables.

## Step 1: Gather Context

- Content type: blog post, case study, portfolio piece, landing page copy, newsletter
- Target audience and their knowledge level
- Goal: thought leadership, lead generation, SEO, client education
- Key message or topic
- Tone: technical, conversational, professional, casual
- SEO keywords (if applicable)
- Word count / length expectation

## Step 2: Content Brief (parallel agents for blog/articles)

**Agent A — "Structure"**: Outline with headline, subheadings, key points per section, CTA. Focus on logical flow and scanability.

**Agent B — "Hook"**: Opening angle, headline variants (5+), unique perspective that differentiates from existing content on the topic.

## Step 3: Content Types

### Blog Post
- Headline: specific, benefit-driven, no clickbait
- Opening: hook in first 2 sentences (stat, question, bold claim)
- Body: subheadings every 2-3 paragraphs, short paragraphs (3-4 sentences max)
- Code examples: real, working, with context — not theoretical
- Closing: summary + clear CTA (not "thanks for reading")

### Case Study
- Structure: Challenge → Approach → Solution → Results
- Include: specific metrics/outcomes, timeline, tech stack used
- Quote from client (if available, or placeholder for one)
- Before/after comparison where visual
- Link to live project (if public)

### Portfolio Piece
- Project overview (1-2 sentences)
- Role and responsibilities
- Tech stack with rationale for choices
- Key challenges and how they were solved
- Results or impact
- Screenshots / visual evidence

## Step 4: Draft & Review

- Write the full draft
- Self-audit: Is it scannable? Does every paragraph earn its place? Is the CTA clear?
- Present to user for review

## Rules

- Write in the user's voice, not generic AI copy
- No filler phrases ("In today's digital landscape...", "Let's dive in...")
- No emojis or icons unless user requests them
- Code examples must be real and working
- SEO-aware but human-first — never keyword-stuff