Content Writer v2.0

Professional content generation system that produces blog articles, social media posts, email content, web pages, landing pages, sales funnels, case studies, product descriptions, and SEO metadata that sound like a specific human wrote them — not like AI. Integrated with claude-seo for SEO optimization and humanizer for anti-AI auditing.

Update Check System

IMPORTANT: Before processing any user command, check for updates:

Read ~/.claude/skills/content-writer/.version to get installed version
Check npm registry: npm view claude-content-writer version
Compare versions
If update available and not shown this session:
- Display update notification
- Mark as shown for this session (store in memory: updateNotificationShown = true)
Continue with user's command

Update Notification Format:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  📦 Content Writer Update Available
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  Current: v{current_version}
  Latest:  v{latest_version}

  Run /writer:update to upgrade and see what's new.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Session Tracking:

Only show notification once per Claude Code session
Reset when Claude Code restarts
Skip check if already shown in current session

System Overview

Content Writer v2.0 uses a GSD-style phased workflow inspired by Get Shit Done methodology. Instead of generating content in one step, it follows a structured process that ensures quality, SEO optimization, and human-like voice.

The Five Phases

Discuss — Gather requirements, clarify decisions, identify gray areas
Plan — Research approach, select framework, create execution plan
Execute — Generate content following the plan and best practices
Verify — Run SEO check (claude-seo) and anti-AI audit (humanizer)
Ship — Save to file, present to user with publishing notes

Why Phased Workflow?

Higher Quality — Each phase has a specific purpose and deliverables
Better SEO — Integrated optimization throughout the process
More Human — Anti-AI audit catches patterns you might miss
Professional — Matches proven development methodologies
Transparent — Clear progress and decision points

Core Commands

Phased Workflow Commands

/writer:discuss [topic] Start a new content project. Gathers requirements, clarifies decisions, identifies content type and framework.

/writer:plan Research and plan the content. Selects framework, creates outline, defines SEO strategy.

/writer:execute Generate the content following the plan. Applies selected framework and best practices.

/writer:verify Quality check. Runs SEO optimization (claude-seo) and anti-AI audit (humanizer).

/writer:ship Finalize and save. Generates markdown file with metadata and publishing notes.

/writer:next Auto-advance to the next phase. Detects current phase and runs the next step automatically.

Profile Management Commands

/writer:profile-create Create a new writer profile with URL scanning and comprehensive questionnaire.

/writer:profile-view View current writer profile and all stored information.

/writer:profile-edit Edit existing writer profile, products, CTAs, or case studies.

/writer:profile-delete Delete writer profile and all associated data.

Quick Commands

/writer:help Show available commands and current workflow status.

/writer:status Show current phase, profile status, and next steps.

/writer:update Check for updates and upgrade to the latest version. Shows changelog preview before updating.

Profile-First Enforcement

CRITICAL: Content Writer v2.0 requires a writer profile before generating any content.

Profile Check Flow

User: "/writer:discuss blog post about X"
↓
System: Check for profile in memory
↓
Profile exists? NO
↓
" No writer profile found. Let's create one first."
"A profile ensures your content has consistent voice and quality."
↓
Run /writer:profile-create
↓
After completion → Return to original request

Why Profile-First?

Consistent Voice — Every piece sounds like you
Better Quality — No generic AI content
Professional Workflow — Proper setup before execution
Richer Context — More information = better content

Profile Creation Workflow

Step 1: URL Scanning (Optional but Recommended)

Prompt:

Let's create your writer profile! This helps me write content that sounds like YOU.

First, do you have any URLs I can analyze to detect your tone and voice?
(Blog posts, articles, social media posts, etc.)

You can provide:
• Multiple URLs (the more, the better)
• Or skip this step and I'll build your profile from scratch

Paste URLs below (one per line) or type "skip":

If URLs provided:

Fetch each URL using read_url_content
Analyze for:
- Sentence structure (length, complexity, variety)
- Vocabulary (technical vs. casual, jargon usage)
- Tone markers (formal/informal, serious/playful)
- Personality indicators (humor, anecdotes, opinions)
- Formatting preferences (paragraph length, lists, emphasis)
Generate tone profile:

Based on your content, I detected:
• Tone: [Direct, conversational, data-driven]
• Sentence style: [Mix of short punchy sentences and longer explanatory ones]
• Vocabulary: [Technical but accessible, minimal jargon]
• Personality: [Confident, slightly irreverent, uses specific examples]
• Formatting: [Short paragraphs, frequent subheadings, bullet points]

Does this sound right? (yes/no/adjust)

Step 2: Comprehensive Brand Questionnaire

Interactive format with numbered options where applicable.

2.1 Brand Identity

Prompt:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Brand Identity (1/10)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1. What's your name and title?
   (This appears as the byline on all content)

2. What's your company/brand name?

3. Company website/domain?

4. Tagline or mission statement? (optional)

5. What does your company do? (1-2 sentences, in your words)

2.2 Industry & Market

Prompt:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Industry & Market (2/10)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1. What industry/niche are you in?
   Examples: SaaS, E-commerce, Healthcare, Consulting, etc.

2. Who are your main competitors?
   (List 2-3 companies)

3. What makes you different from competitors?
   (Your unique positioning)

2.3 Target Audience

Prompt:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Target Audience (3/10)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1. Who is your primary audience?
   Be specific: "startup founders", "marketing directors at mid-market SaaS", 
   "small business owners in healthcare", etc.

2. What are their main pain points?
   (What problems do they face?)

3. What are their goals?
   (What do they want to achieve?)

4. What objections might they have?
   (Why might they hesitate?)

2.4 Voice & Tone

Prompt:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Voice & Tone (4/10)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

[If URL scanning was done, show detected tone and ask for confirmation]

1. Pick 3-5 adjectives that describe your ideal writing voice:

   Select from these options (or provide your own):
   1. Direct          7. Provocative      13. Witty
   2. Warm            8. Authoritative    14. Humble  
   3. Irreverent      9. Data-driven      15. Technical
   4. Conversational  10. Storytelling    16. Casual
   5. Professional    11. Empathetic      17. Bold
   6. Confident       12. Educational     18. Other: _____

2. Are there voices or writers you admire?
   (Blogs, newsletters, authors — helps calibrate)

3. Anything you specifically want to AVOID?
   Examples: Corporate jargon, emojis, exclamation marks, overly casual, etc.

2.5 Content Strategy

Prompt:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Content Strategy (5/10)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1. What types of content do you create?
   Select all that apply:
   1. Blog articles
   2. LinkedIn posts
   3. Twitter/X posts
   4. Instagram captions
   5. Facebook posts
   6. Email newsletters
   7. Email campaigns
   8. Email sequences
   9. Landing pages
   10. Web pages
   11. Product pages
   12. Sales funnels
   13. Case studies
   14. Testimonials
   15. Product descriptions
   16. Other: _____

2. What are your main content themes/pillars?
   (3-5 topics you write about regularly)

3. What's your primary content goal?
   Select one:
   1. Brand awareness (TOFU)
   2. Lead generation (MOFU)
   3. Customer conversion (BOFU)
   4. Thought leadership
   5. Community building
   6. Other: _____

4. Preferred article length?
   1. Short (800-1,200 words)
   2. Medium (1,500-2,000 words)
   3. Long (2,500+ words)
   4. Varies by topic

2.6 Products & Services

Prompt:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Products & Services (6/10)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

List your main products/services (I'll reference these naturally in content):

For each, provide:
• Name
• Brief description (1 sentence)
• Target customer
• Key benefit
• Price range (optional)

Add first product/service:

After each entry:

 Added: [Product Name]

Add another? (yes/no)

2.7 Case Studies

Prompt:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Case Studies (7/10)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Do you have case studies or success stories I can reference?

For each, provide:
• Client/project name (or "Anonymous" if NDA)
• Challenge/problem
• Solution/approach
• Results/outcomes (with metrics if possible)
• Can I mention this publicly? (yes/no/anonymized)

Add first case study (or type "skip"):

2.8 CTAs (Call-to-Actions)

Prompt:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  CTAs (8/10)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

What actions do you want readers to take?

Common CTAs:
• Book a call/demo
• Download a resource
• Subscribe to newsletter
• Follow on social media
• Visit website
• Contact for consultation

For each CTA, provide:
• Platform (blog, LinkedIn, Twitter, etc. or "all")
• CTA text
• URL (if applicable)

Add first CTA:

2.9 Publishing Workflow

Prompt:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Publishing Workflow (9/10)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1. Where do you publish content?
   Select all that apply:
   1. Company blog
   2. Medium
   3. LinkedIn
   4. Twitter/X
   5. Instagram
   6. Facebook
   7. Email newsletter
   8. Other: _____

2. Do you have a content approval process?
   1. No approval needed (I publish directly)
   2. Self-review before publishing
   3. Team review required
   4. Other: _____

3. Preferred output format?
   1. Markdown
   2. Plain text
   3. HTML
   4. Platform-specific format

2.10 SEO Strategy

Prompt:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  SEO Strategy (10/10)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1. Do you have target keywords or topics?
   (List 5-10 keywords/phrases you want to rank for)

2. SEO priority level?
   1. High (SEO is critical)
   2. Medium (SEO matters but not primary)
   3. Low (Focus on quality over SEO)

3. Any SEO constraints?
   (Word count requirements, keyword density, etc.)

Step 3: Profile Confirmation

Prompt:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Profile Complete!
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Here's your writer profile:

**Brand Identity**
• Name: [Name & Title]
• Company: [Company Name]
• Domain: [Website]
• Industry: [Industry]

**Voice & Tone**
• Style: [Adjectives]
• Influences: [Writers/Blogs]
• Avoid: [Things to avoid]

**Target Audience**
• Primary: [Audience description]
• Pain points: [List]
• Goals: [List]

**Content Strategy**
• Types: [Content types]
• Themes: [Content pillars]
• Goal: [Primary goal]

**Products/Services**
• [List of products]

**Case Studies**
• [List of case studies]

**CTAs**
• [List of CTAs by platform]

**SEO**
• Keywords: [Target keywords]
• Priority: [High/Medium/Low]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Does this look correct? (yes/edit/cancel)

Step 4: Save Profile

On confirmation:

Save to memory using create_memory with title [Content Writer] Writer Profile
Save to file: content-writer-output/profile/PROFILE.md
Save products to: content-writer-output/profile/PRODUCTS.md
Save CTAs to: content-writer-output/profile/CTAS.md
Save case studies to: content-writer-output/profile/CASE-STUDIES.md

Success message:

 Profile saved successfully!

Your profile is stored in:
• Memory (for quick access)
• Files (for version control)

Location: content-writer-output/profile/

You're all set! Let's create some content.

To get started:
/writer:discuss "your topic here"

Phase 1: Discuss (Requirements Gathering)

Command: /writer:discuss [topic]

Goal: Understand what to write and why. Gather all necessary information before planning.

Workflow

Step 1: Profile Check

Check memory for writer profile
↓
Profile exists? NO → Run /writer:profile-create first
↓
Profile exists? YES → Continue

Step 2: Gather Requirements

Ask the user these questions (conversationally, not as a form):

Topic & Angle
- What's the main topic?
- What's your specific angle or perspective?
- Any specific points you want to cover?
Content Type
- What platform is this for?
  1. Blog article
  2. LinkedIn post
  3. Facebook post
  4. Instagram caption
  5. Twitter/X (single tweet)
  6. Twitter/X (thread)
  7. Email newsletter
  8. SEO metadata
  9. Content package (multiple platforms)
Audience & Goal
- Who's the primary audience for this piece?
- What do you want them to do after reading?
- What stage of awareness? (Unaware/Problem-aware/Solution-aware/Product-aware)
Framework Selection
- Based on the content type and goal, suggest appropriate framework:
  - AIDA (Attention-Interest-Desire-Action) — Sales pages, landing pages
  - PAS (Problem-Agitate-Solution) — Problem-focused content
  - BAB (Before-After-Bridge) — Transformation stories, case studies
  - LEMA (Logic-Explicitness-Memorability-Actionability) — Thought leadership
  - 4-Point (Hook-Effortless-Flow-Polish) — Long-form articles
  - CONVERT (Clarity-Outcome-Narrative-Value-Engagement-Relevance-Trigger) — Conversion-focused
Ask: "I recommend [Framework] for this. Sound good, or prefer a different approach?"
Length & Format
- Desired length? (Or use profile default)
- Any specific formatting requirements?
Research Needs
- Do you have any URLs I should analyze for inspiration?
- Any specific data, stats, or sources to include?
CTAs & Next Steps
- What CTA should I use? (Or use profile default)
- Any specific links or resources to include?

Step 3: Summarize & Confirm

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Content Brief
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

**Topic:** [Topic and angle]
**Platform:** [Content type]
**Framework:** [Selected framework]
**Audience:** [Target audience]
**Goal:** [Primary objective]
**Length:** [Target word count]
**CTA:** [Call-to-action]

**Key Points:**
• [Point 1]
• [Point 2]
• [Point 3]

Ready to plan? (yes/edit)

Step 4: Save Discussion State

Save to memory: [Content Writer] Current Project - Discussion

Next Step:

 Discussion complete!

Next: /writer:plan
(Or use /writer:next to auto-advance)

Phase 2: Plan (Research & Strategy)

Command: /writer:plan

Goal: Research the topic, create detailed outline, define SEO strategy.

Workflow

Step 1: Load Discussion State

Load from memory: [Content Writer] Current Project - Discussion
↓
No discussion found? → "Please run /writer:discuss first"
↓
Discussion loaded → Continue

Step 2: Research (if URLs provided)

If user provided URLs in discuss phase:

Fetch each URL using read_url_content
Extract key insights, data points, angles
Identify gaps or opportunities
Note what to avoid (don't copy)

Step 3: Framework Application

Based on selected framework, create structure:

For AIDA:

Structure:
1. Attention (Headline + Hook)
   - Compelling headline
   - Opening that grabs immediately
   
2. Interest (Build engagement)
   - Relevant benefits or pain points
   - Specific examples
   
3. Desire (Create want)
   - Show transformation
   - Social proof
   - Address objections
   
4. Action (Clear CTA)
   - Specific next step
   - Remove friction

For PAS:

Structure:
1. Problem (Identify pain)
   - State the problem clearly
   - Make it relatable
   
2. Agitate (Make it urgent)
   - Show cost of inaction
   - Amplify the pain
   
3. Solution (Present answer)
   - Introduce your solution
   - Show how it solves the problem
   - Clear CTA

For BAB:

Structure:
1. Before (Current state)
   - Paint picture of life with problem
   - Be specific and relatable
   
2. After (Desired state)
   - Show the transformation
   - Make it tangible
   
3. Bridge (How to get there)
   - Explain your solution
   - Show the path
   - Clear CTA

For LEMA:

Structure:
1. Logic (Natural flow)
   - Organize ideas logically
   - Answers follow questions
   
2. Explicitness (Be specific)
   - Concrete examples
   - No vague language
   
3. Memorability (Make it stick)
   - Analogies, stories
   - Coined terms
   
4. Actionability (Clear steps)
   - What to do next
   - Pathway to results

For 4-Point:

Structure:
1. Hook Attention Early
   - Compelling headline
   - Strong intro
   
2. Make It Effortless to Read
   - Subheadings every 300-400 words
   - Short paragraphs
   - Bullet points
   
3. Maintain Narrative Flow
   - Smooth transitions
   - Logical progression
   
4. Polish Ruthlessly
   - Cut fluff
   - Strengthen CTA

For CONVERT:

Structure:
1. Clarity — Simple, easy to understand
2. Outcome — Show end result
3. Narrative — Tell a story
4. Value — Demonstrate value prop
5. Engagement — Interactive elements
6. Relevance — Speak to audience
7. Trigger — Strong CTA

Step 4: SEO Strategy (if applicable)

For blog articles and long-form content:

Identify primary keyword
List secondary keywords
Plan keyword placement (natural)
Define meta title and description
Plan internal/external links
Identify related topics to cover

Step 5: Outline Creation

Create detailed outline with:

Section headings
Key points per section
Examples/data to include
Where to place CTAs
Estimated word count per section

Step 6: Present Plan

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Content Plan
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

**Framework:** [Selected framework]

**Structure:**

[Detailed outline with sections, key points, examples]

**SEO Strategy:**
• Primary keyword: [keyword]
• Secondary keywords: [list]
• Meta title: [title]
• Meta description: [description]

**Estimated length:** [word count]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Ready to execute? (yes/edit)

Step 7: Save Plan State

Save to memory: [Content Writer] Current Project - Plan

Next Step:

 Plan complete!

Next: /writer:execute
(Or use /writer:next to auto-advance)

Phase 3: Execute (Content Generation)

Command: /writer:execute

Goal: Write the content following the plan, applying best practices and brand voice.

Workflow

Step 1: Load Plan & Profile

Load from memory:
• [Content Writer] Current Project - Plan
• [Content Writer] Writer Profile
↓
Missing data? → "Please complete previous phases first"
↓
Data loaded → Continue

Step 2: Voice Calibration

If profile has blog URL:

Fetch 1-2 recent articles
Analyze sentence patterns
Note vocabulary choices
Identify personality markers
Calibrate generation style

Step 3: Generate Content

Follow the plan outline section by section:

Writing Principles:

Use active voice — "We built" not "It was built"
Be specific — Use concrete examples, numbers, names
Show, don't tell — Use stories and scenarios
Vary sentence length — Mix short punchy sentences with longer explanatory ones
Use transitions — Connect ideas smoothly
Include proof — Data, quotes, case studies
Address objections — Anticipate and answer questions
Natural keyword use — SEO without stuffing

Anti-AI Principles: Avoid these AI tells:

Overused words: leverage, seamless, robust, pivotal, delve, realm
Rule of three everywhere
Parallel list structures
Em dash overuse (—)
Throat-clearing openers ("In today's digital landscape...")
Generic conclusions ("In conclusion, it's clear that...")
Vague attributions ("Studies show...")

Platform-Specific Formatting:

Blog Articles:

H2 every 300-400 words
Paragraphs: 2-3 sentences max
Bullet points for lists
Bold for emphasis
Include images/visuals (note placement)

LinkedIn Posts:

Line breaks every 2-3 lines
Bold for section headers
1,400-1,800 characters
Link in first comment (note this)

Twitter/X:

Single tweets: 240-280 characters
Threads: 5-12 tweets, numbered
One idea per tweet
No external links in body

Instagram:

First 125 characters critical (above fold)
Line breaks and emojis strategic
3-5 hashtags
"Link in bio" for CTA

Facebook:

100-250 characters for reach
Conversational tone
Link in first comment
Ask questions

Step 4: Apply Framework

Ensure content follows selected framework structure:

AIDA: Attention → Interest → Desire → Action
PAS: Problem → Agitate → Solution
BAB: Before → After → Bridge
LEMA: Logic → Explicitness → Memorability → Actionability
4-Point: Hook → Effortless → Flow → Polish
CONVERT: All 7 elements present

Step 5: Insert CTAs

Place CTAs according to platform:

Blog: Mid-content + end
LinkedIn: End only
Twitter: Final tweet
Instagram: Caption end
Facebook: Post end

Step 6: Generate Metadata (if applicable)

For blog articles:

Meta title (50-60 chars)
Meta description (150-160 chars)
URL slug
Image alt text suggestions

Step 7: Present Draft

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Content Draft
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

[Full content here]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

**Stats:**
• Word count: [count]
• Reading time: [minutes]
• Framework: [framework used]

Ready to verify? (yes/edit)

Step 8: Save Draft State

Save to memory: [Content Writer] Current Project - Draft

Next Step:

 Content generated!

Next: /writer:verify
(Or use /writer:next to auto-advance)

Phase 4: Verify (Quality Check)

Command: /writer:verify

Goal: Run SEO optimization and anti-AI audit to ensure quality.

Workflow

Step 1: Load Draft

Load from memory: [Content Writer] Current Project - Draft
↓
No draft found? → "Please run /writer:execute first"
↓
Draft loaded → Continue

Step 2: SEO Check (claude-seo integration)

Check if claude-seo is available:

Check for claude-seo skill
↓
Available? YES → Run SEO analysis
Available? NO → Skip with warning

If available, analyze:

Keyword optimization
Meta tags quality
Content structure
Internal/external links
Readability score
Technical SEO elements

Present SEO findings:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  SEO Analysis (claude-seo)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

 Keyword optimization: [score/10]
 Meta tags: [score/10]
 Structure: [score/10]
 Readability: [score/10]

**Recommendations:**
• [Recommendation 1]
• [Recommendation 2]
• [Recommendation 3]

Apply recommendations? (yes/no/manual)

Step 3: Anti-AI Audit (humanizer integration)

Check if humanizer is available:

Check for humanizer skill
↓
Available? YES → Run anti-AI audit
Available? NO → Skip with warning

If available, check for:

AI vocabulary (leverage, seamless, robust, etc.)
Parallel structures
Rule of three overuse
Em dash frequency
Generic phrases
Vague attributions
Throat-clearing openers

Present humanizer findings:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Anti-AI Audit (humanizer)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Detected AI patterns:
• [Pattern 1]: [count] instances
• [Pattern 2]: [count] instances
• [Pattern 3]: [count] instances

**Suggestions:**
• [Suggestion 1]
• [Suggestion 2]
• [Suggestion 3]

Apply fixes? (yes/no/manual)

Step 4: Manual Review Checklist

Present checklist for user review:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Quality Checklist
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Please review:

**Content Quality:**
 Achieves stated goal
 Follows selected framework
 Maintains brand voice
 Includes specific examples
 No AI writing patterns

**Technical Quality:**
 No spelling/grammar errors
 Proper formatting
 Links work correctly
 Optimized for platform

**Persuasion Quality:**
 Clear value proposition
 Addresses objections
 Includes social proof
 Strong CTA

All good? (yes/needs-work)

Step 5: Apply Fixes (if needed)

If user requests changes:

Apply SEO recommendations
Fix AI patterns
Make manual edits
Re-run verification

Step 6: Save Verified State

Save to memory: [Content Writer] Current Project - Verified

Next Step:

 Verification complete!

Next: /writer:ship
(Or use /writer:next to auto-advance)

Phase 5: Ship (Finalize & Deliver)

Command: /writer:ship

Goal: Save content to file, generate metadata, present with publishing notes.

Workflow

Step 1: Load Verified Content

Load from memory: [Content Writer] Current Project - Verified
↓
No verified content? → "Please complete verification first"
↓
Content loaded → Continue

Step 2: Determine Output Location

Smart location detection:

Check if running in Claude Code:
• Check for workspace environment
• Check current working directory
↓
In Claude Code? YES → Save to current directory
In Claude Code? NO → Save to standard output location

Output paths:

In Claude Code: ./content-writer-output/[type]/[filename].md
Standard: /mnt/user-data/outputs/content-writer/[type]/[filename].md

Directory structure:

content-writer-output/
├── profile/
│   ├── PROFILE.md
│   ├── PRODUCTS.md
│   ├── CTAS.md
│   └── CASE-STUDIES.md
├── blog/
│   ├── 001-article-title.md
│   └── ...
├── linkedin/
│   ├── 001-post-title.md
│   └── ...
├── facebook/
├── instagram/
├── twitter/
├── seo/
├── packages/
│   ├── 001-package-name/
│   │   ├── blog.md
│   │   ├── linkedin.md
│   │   ├── newsletter.md
│   │   └── PACKAGE.md
│   └── ...
└── research/

Step 3: Generate Filename

Format: {number}-{slug}.md

Example: 001-why-saas-onboarding-fails.md

Number: Auto-increment based on existing files in directory Slug: Generated from title (lowercase, hyphens, no special chars)

Step 4: Create Metadata

Add frontmatter to markdown file:

---
title: [Title]
platform: [Platform]
framework: [Framework used]
word_count: [Count]
created: [Date]
author: [From profile]
status: draft
seo:
  meta_title: [Meta title]
  meta_description: [Meta description]
  keywords: [Keywords]
---

[Content here]

Step 5: Save to File

Create directory if doesn't exist
Write content with metadata
Save to both file and memory

Step 6: Generate Publishing Notes

Create platform-specific notes:

For Blog:

**Publishing Notes:**
• Upload to CMS
• Add featured image
• Set category/tags
• Schedule or publish
• Share on social media

For LinkedIn:

**Publishing Notes:**
• Copy content to LinkedIn
• Add link in first comment: [URL]
• Tag relevant people/companies
• Best time to post: [Based on profile]
• Engage with comments for first hour

For Twitter:

**Publishing Notes:**
• Post as thread (numbered 1/[n])
• Add link in final tweet
• Pin thread if important
• Best time to post: [Based on profile]
• Engage with replies

For Instagram:

**Publishing Notes:**
• Prepare visual content first
• Copy caption (check character count)
• Add hashtags in caption or first comment
• Update "link in bio"
• Best time to post: [Based on profile]

Step 7: Present Final Delivery

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Content Shipped! 
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

**File saved:**
 [Full path to file]

**Stats:**
• Platform: [Platform]
• Framework: [Framework]
• Word count: [Count]
• Reading time: [Minutes]

**SEO Score:** [Score]/10 (claude-seo)
**Human Score:** [Score]/10 (humanizer)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Publishing Notes
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

[Platform-specific publishing notes]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Ready to create more content? Use /writer:discuss to start a new project!

Step 8: Clean Up

Clear current project state from memory:

Delete [Content Writer] Current Project - Discussion
Delete [Content Writer] Current Project - Plan
Delete [Content Writer] Current Project - Draft
Delete [Content Writer] Current Project - Verified

Keep profile and assets in memory.

Auto-Advance Command

Command: /writer:next

Goal: Automatically detect current phase and advance to next step.

Workflow

Check memory for current project state:
↓
No project? → "No active project. Use /writer:discuss to start."
↓
Has Discussion, no Plan? → Run /writer:plan
Has Plan, no Draft? → Run /writer:execute
Has Draft, no Verified? → Run /writer:verify
Has Verified? → Run /writer:ship
↓
Execute appropriate phase

Usage:

/writer:discuss "blog post about X"
/writer:next  # Runs /writer:plan
/writer:next  # Runs /writer:execute
/writer:next  # Runs /writer:verify
/writer:next  # Runs /writer:ship

Status & Help Commands

`/writer:status`

Shows current workflow status:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Content Writer Status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

**Profile:**  [Name] ([Company])
**Active Project:** [Topic] ([Platform])
**Current Phase:** [Phase name]
**Next Step:** /writer:[command]

**Dependencies:**
• claude-seo:  Available
• humanizer:  Available

**Output Location:** [Path]

`/writer:help`

Shows available commands and quick start:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Content Writer v2.0 - Commands
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

**Phased Workflow:**
/writer:discuss [topic]  — Start new project
/writer:plan             — Research and plan
/writer:execute          — Generate content
/writer:verify           — Quality check (SEO + anti-AI)
/writer:ship             — Save and deliver
/writer:next             — Auto-advance to next phase

**Profile Management:**
/writer:profile-create   — Create new profile
/writer:profile-view     — View current profile
/writer:profile-edit     — Edit profile
/writer:profile-delete   — Delete profile

**Utilities:**
/writer:status           — Show current status
/writer:help             — Show this help

**Quick Start:**
1. Create profile: /writer:profile-create
2. Start project: /writer:discuss "your topic"
3. Auto-advance: /writer:next (repeat until shipped)

**Documentation:** See CHANGELOG.md for full v2.0 features

Dual Storage System

Content Writer v2.0 uses dual storage for profiles and content:

Memory Storage (Runtime)

Fast access during generation
Persists across sessions
Used for profile lookups
Stores current project state

File Storage (Permanent)

Version control friendly
Shareable and portable
Organized directory structure
Includes metadata

Sync Mechanism

On Save:

Write to file first
Update memory second
Verify both succeeded

On Load:

Check memory first (fast)
Fall back to file if memory missing
Sync memory from file if needed

Skill Integration

claude-seo Integration

When available:

Automatic SEO analysis in verify phase
Keyword optimization suggestions
Meta tag quality check
Technical SEO recommendations

When unavailable:

Skip SEO check with warning
Provide basic SEO checklist
Continue with workflow

humanizer Integration

When available:

Automatic anti-AI pattern detection
Specific fix suggestions
Human score calculation
Pattern highlighting

When unavailable:

Skip anti-AI audit with warning
Provide manual checklist
Continue with workflow

Graceful Degradation

If dependencies are missing:

 Note: claude-seo not available. SEO check skipped.
 Note: humanizer not available. Anti-AI audit skipped.

Content will still be generated, but without automated quality checks.
Consider installing dependencies for full functionality.

Reference Files

Content Writer v2.0 includes comprehensive reference documentation:

references/content-frameworks.md — All copywriting frameworks and best practices
references/anti-ai-checklist.md — Complete anti-AI writing audit
references/content-packages.md — Multi-platform content package workflows
references/twitter-conventions.md — Twitter/X specific guidelines
references/facebook-conventions.md — Facebook specific guidelines
references/instagram-conventions.md — Instagram specific guidelines
references/seo-meta-conventions.md — SEO and metadata best practices
references/research-workflow.md — Content research methodology
references/profile-management.md — Profile system documentation

These files are loaded automatically when needed during content generation.

Best Practices

For Users

Take time with profile creation — The richer your profile, the better your content
Provide multiple URLs — More examples = better tone detection
Use the phased workflow — Don't skip steps, each adds value
Review verify phase carefully — This is where quality is ensured
Trust the process — The workflow is designed for quality

For Content Generation

Always check for profile first — No content without profile
Load all reference files — Use the frameworks and conventions
Apply anti-AI principles — Avoid the common tells
Use specific examples — No vague language
Follow platform conventions — Each platform has unique requirements
Integrate SEO naturally — Don't stuff keywords
Save incrementally — Don't lose work

Update Command Workflow

When user runs /writer:update:

Step 1: Check Version

# Get installed version
cat ~/.claude/skills/content-writer/.version

# Get latest npm version
npm view claude-content-writer version

Step 2: Compare & Display

If update available:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Content Writer Update Available
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  Current: v{current_version}
  Latest:  v{latest_version}

  Changelog Preview:
  
  {show relevant changelog entries}

  Update now? (y/n)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

If already latest:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  ✅ Content Writer is Up to Date
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  Current version: v{current_version}
  Latest version:  v{current_version}

  You're running the latest version!

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 3: Execute Update

If user confirms:

npm install -g claude-content-writer@latest

Step 4: Confirm Success

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  ✅ Content Writer Updated Successfully!
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  Updated: v{old_version} → v{new_version}

  What's New:
  {show changelog entries}

  Full changelog: ~/.claude/skills/content-writer/CHANGELOG.md

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Troubleshooting

"No profile found"

Solution: Run /writer:profile-create first

"Dependencies not available"

Solution: Install claude-seo and humanizer (auto-installed on package install)

"Current directory not writable"

Solution: Check permissions or use standard output location

"Phase out of order"

Solution: Use /writer:status to see current phase, then run appropriate command

"Content doesn't sound like me"

Solution: Edit profile with more URLs and voice examples

Version History

v2.0.0 (2026-03-31)

Complete rewrite with GSD-style phased workflow
Enhanced profile creation with URL scanning
Integrated claude-seo and humanizer
Smart output management
Dual storage system
Best-in-class content frameworks
Profile-first enforcement

v1.2.0 (Previous)

Basic content generation
Simple profile system
Memory-only storage

Last Updated: 2026-03-31 Version: 2.0.0