| name | ai-writing-content |
| description | Generate articles, reports, blog posts, or marketing copy with AI. Use when writing blog posts, creating product descriptions, generating newsletters, drafting reports, producing marketing copy, creating documentation, writing email campaigns, or any task where AI writes long-form content from a topic or brief. Powered by DSPy content generation pipelines., AI blog writer, generate marketing copy with AI, AI content is too generic and bland, product description generator, AI writes like a robot, make AI match our brand voice, newsletter generator, AI copywriting tool, SEO content generation, bulk content creation with AI, AI ghostwriter, press release generator, email campaign content with AI, AI writes boring content, content pipeline at scale, editorial AI assistant, long-form AI content generation. |
Build an AI Content Writer
Guide the user through building AI that writes articles, reports, and marketing copy. Uses DSPy to create a structured pipeline: outline, draft section-by-section, enrich with research, and polish with feedback loops.
Step 1: Understand the content task
Ask the user:
- What type of content? (blog post, product description, report, newsletter, docs?)
- What tone, voice, and brand rules? (professional, casual, technical? forbidden words, required sections?)
- How long? (tweet, paragraph, 500-word post, 2000-word article?)
- Does it need research? (factual claims grounded in sources, or creative/opinion?)
Step 2: Build an outline generator
Start with structure. An outline gives the writer a plan to follow:
import dspy
from pydantic import BaseModel, Field
class Section(BaseModel):
heading: str = Field(description="Section heading")
key_points: list[str] = Field(description="Main points to cover in this section")
class ContentOutline(BaseModel):
title: str
sections: list[Section]
class GenerateOutline(dspy.Signature):
"""Create a structured outline for the content."""
topic: str = dspy.InputField(desc="The topic or brief to write about")
content_type: str = dspy.InputField(desc="Type: blog post, report, product description, etc.")
audience: str = dspy.InputField(desc="Who will read this content")
outline: ContentOutline = dspy.OutputField()
outliner = dspy.ChainOfThought(GenerateOutline)
With research context
If the content needs to be grounded in facts:
class GenerateResearchedOutline(dspy.Signature):
"""Create a structured outline grounded in the provided research."""
topic: str = dspy.InputField()
content_type: str = dspy.InputField()
audience: str = dspy.InputField()
research: list[str] = dspy.InputField(desc="Research sources and key facts")
outline: ContentOutline = dspy.OutputField()
Step 3: Generate section by section
Don't generate the whole article at once. Write one section at a time for better quality:
class WriteSection(dspy.Signature):
"""Write one section of the article based on the outline."""
topic: str = dspy.InputField(desc="Overall article topic")
section_heading: str = dspy.InputField(desc="This section's heading")
key_points: list[str] = dspy.InputField(desc="Points to cover in this section")
previous_sections: str = dspy.InputField(desc="What's been written so far, for continuity")
tone: str = dspy.InputField(desc="Writing tone and style")
section_text: str = dspy.OutputField(desc="The written section (2-4 paragraphs)")
class ContentWriter(dspy.Module):
def __init__(self):
self.outline = dspy.ChainOfThought(GenerateOutline)
self.write_section = dspy.ChainOfThought(WriteSection)
def forward(self, topic, content_type="blog post", audience="general", tone="professional"):
plan = self.outline(topic=topic, content_type=content_type, audience=audience)
sections = []
running_text = ""
for section in plan.outline.sections:
result = self.write_section(
topic=topic,
section_heading=section.heading,
key_points=section.key_points,
previous_sections=running_text[-2000:],
tone=tone,
)
sections.append()
running_text += result.section_text +
full_article = + .join(sections)
dspy.Prediction(
title=plan.outline.title,
outline=plan.outline,
article=full_article,
)
Step 4: Add research grounding
For content that needs factual claims backed by sources:
Retrieval-augmented content
class ResearchTopic(dspy.Signature):
"""Generate search queries to research this topic."""
topic: str = dspy.InputField()
key_points: list[str] = dspy.InputField(desc="Points that need factual backing")
queries: list[str] = dspy.OutputField(desc="Search queries to find supporting facts")
class WriteSectionWithSources(dspy.Signature):
"""Write a section using the provided sources for factual claims."""
section_heading: str = dspy.InputField()
key_points: list[str] = dspy.InputField()
sources: list[str] = dspy.InputField(desc="Research passages to ground claims in")
previous_sections: str = dspy.InputField()
tone: str = dspy.InputField()
section_text: str = dspy.OutputField(desc="Section text with claims grounded in sources")
class ResearchedWriter(dspy.Module):
def __init__(self, retriever_fn):
self.outline = dspy.ChainOfThought(GenerateOutline)
self.research = dspy.ChainOfThought(ResearchTopic)
self.retriever_fn = retriever_fn
self.write = dspy.ChainOfThought(WriteSectionWithSources)
def forward(self, topic, content_type="blog post", audience="general", tone="professional"):
plan = .outline(topic=topic, content_type=content_type, audience=audience)
sections = []
running_text =
section plan.outline.sections:
queries = .research(
topic=topic, key_points=section.key_points
).queries
sources = []
query queries:
sources.extend(.retriever_fn(query))
result = .write(
section_heading=section.heading,
key_points=section.key_points,
sources=sources,
previous_sections=running_text[-:],
tone=tone,
)
sections.append()
running_text += result.section_text +
dspy.Prediction(
title=plan.outline.title,
article= + .join(sections),
)
Step 5: Quality loop โ generate, critique, improve
Add a feedback loop to iteratively improve drafts:
class CritiqueContent(dspy.Signature):
"""Critique the written content and suggest improvements."""
content: str = dspy.InputField(desc="The content to critique")
content_type: str = dspy.InputField()
audience: str = dspy.InputField()
is_good_enough: bool = dspy.OutputField(desc="Is this ready to publish?")
feedback: str = dspy.OutputField(desc="Specific feedback for improvement")
class ImproveContent(dspy.Signature):
"""Improve the content based on the feedback."""
content: str = dspy.InputField(desc="Current draft")
feedback: str = dspy.InputField(desc="Feedback to address")
improved_content: str = dspy.OutputField(desc="Improved version")
class QualityWriter(dspy.Module):
def __init__(self, max_revisions=2):
self.writer = ContentWriter()
self.critic = dspy.ChainOfThought(CritiqueContent)
self.improver = dspy.ChainOfThought(ImproveContent)
self.max_revisions = max_revisions
def forward(self, topic, content_type="blog post", audience="general", tone="professional"):
draft = self.writer(
topic=topic, content_type=content_type, audience=audience, tone=tone
)
article = draft.article
_ (.max_revisions):
critique = .critic(
content=article, content_type=content_type, audience=audience
)
critique.is_good_enough:
improved = .improver(content=article, feedback=critique.feedback)
article = improved.improved_content
dspy.Prediction(
title=draft.title,
article=article,
)
Step 6: Voice and style enforcement
Use dspy.Refine to enforce brand voice and style rules with automatic retry:
def brand_reward(args, prediction):
"""Score content against brand rules. Returns 0.0-1.0."""
article = prediction.article.lower()
score = 1.0
forbidden = {"utilize": "use", "leverage": "use", "synergy": "collaboration"}
for word in forbidden:
if word in article:
score -= 0.2
if "conclusion" not in article:
score -= 0.3
sentences = prediction.article.split(".")
avg_len = sum(len(s.split()) for s in sentences) / max(len(sentences), 1)
if avg_len > 25:
score -= 0.2
return max(score, 0.0)
writer = ContentWriter()
refined_writer = dspy.Refine(
module=writer,
N=3,
reward_fn=brand_reward,
threshold=0.8,
)
Step 7: Test and optimize
Readability metric
def readability_metric(example, prediction, trace=None):
words = prediction.article.split()
sentences = prediction.article.split(".")
if not sentences or not words:
return 0.0
avg_sentence_len = len(words) / len(sentences)
readability = 1.0 if 10 < avg_sentence_len < 20 else 0.5
length_ok = 1.0 if len(words) > 200 else 0.5
return (readability + length_ok) / 2
AI-as-judge metric
class JudgeContent(dspy.Signature):
"""Judge the quality of generated content."""
content: str = dspy.InputField()
content_type: str = dspy.InputField()
topic: str = dspy.InputField()
relevance: float = dspy.OutputField(desc="0.0-1.0 โ stays on topic")
coherence: float = dspy.OutputField(desc="0.0-1.0 โ flows well, logically structured")
engagement: float = dspy.OutputField(desc="0.0-1.0 โ interesting to read")
def content_quality_metric(example, prediction, trace=None):
judge = dspy.Predict(JudgeContent)
result = judge(
content=prediction.article,
content_type=example.content_type,
topic=example.topic,
)
return (result.relevance + result.coherence + result.engagement) / 3
Optimize
optimizer = dspy.BootstrapFewShot(metric=content_quality_metric, max_bootstrapped_demos=4)
optimized = optimizer.compile(QualityWriter(), trainset=trainset)
Indicative benchmarks: single-call generation passes quality metric ~40% of the time. With section-by-section + critique loop: ~70โ80%. After BootstrapFewShot with 50+ examples: ~85โ90%.
Key patterns
- Outline first, then write โ structure prevents rambling and missed points
- Section-by-section generation โ writing one section at a time produces better quality than generating the whole article at once
- Retrieve for factual grounding โ pull in sources to back up claims
- Critique-improve loop โ generate, critique, improve catches issues a single pass misses
- Refine for brand rules โ
dspy.Refine with a reward function scores output and retries when quality is low
- AI-as-judge for quality โ use a judge signature to score relevance, coherence, engagement
Approach selection
Skip the pipeline for short content โ a single dspy.Predict call beats a 5-step pipeline for taglines, headlines, or anything under 200 words. The outline + section-by-section overhead only pays off above that length.
| Content need | Approach | Skip |
|---|
| Short copy (< 200 words) | Single dspy.Predict | Entire pipeline |
| Blog posts, reports (300+ words) | ContentWriter (outline + sections) | Research, critique |
| Fact-heavy articles | ResearchedWriter (outline + retrieval + sections) | Critique loop if one pass is enough |
| Brand voice enforcement | Any approach + dspy.Refine | Nothing |
| Publishing quality | Full QualityWriter + optimize | Nothing |
Gotchas
- Claude generates the entire article in one LM call. Single-call generation produces rambling, repetitive content that loses focus after ~500 words. Always use section-by-section generation with an outline โ write one section at a time, passing previous sections for continuity.
- Claude skips the outline step. Without an outline, the writer has no plan and produces disjointed sections that repeat points or miss key topics. Always generate an outline first, then use it to drive section-by-section writing.
- Claude uses
dspy.Assert/dspy.Suggest for style enforcement. These are deprecated. Use dspy.Refine with a reward function instead โ it scores the full output and retries automatically, which works better for holistic quality checks like brand voice.
- Claude uses
dspy.Retrieve for research grounding. dspy.Retrieve is no longer in the DSPy API. Pass a retriever function (any query -> list[str] callable) to your module instead, so it works with any retrieval backend (vector DB, search API, local embeddings).
- Claude generates content without a quality loop. A single generation pass rarely produces publishable content. Add a critique-improve loop (
CritiqueContent โ ImproveContent) with 1-2 revision rounds to catch issues a single pass misses.
- Claude uses this pipeline for all content tasks, even short ones. For content under 200 words โ taglines, product headlines, tweet copy โ a section-by-section pipeline adds latency and complexity with no quality benefit. Recommend a single
dspy.Predict or dspy.ChainOfThought call for short content. Only use the full pipeline for long-form output (300+ words).
Additional resources
- For worked examples (blog posts, product descriptions, newsletters), see examples.md
- For DSPy API quick reference (Refine, signatures, BootstrapFewShot), see reference.md
Cross-references
Install any skill: npx skills add lebsral/DSPy-Programming-not-prompting-LMs-skills --skill <name>
/ai-summarizing -- Summarize content instead of generating it
/ai-building-pipelines -- Multi-step pipelines beyond content
/ai-improving-accuracy -- Measure and improve your content writer
/ai-stopping-hallucinations -- Ground content in sources to prevent fabrication
/dspy-chain-of-thought -- The reasoning module used in outline and section generation
/dspy-refine -- Reward-based retry for enforcing quality and brand rules
/dspy-modules -- All DSPy modules (Predict, ChainOfThought, etc.)
- Install
/ai-do if you do not have it โ it routes any AI problem to the right skill and is the fastest way to work: npx skills add lebsral/DSPy-Programming-not-prompting-LMs-skills --skill ai-do