This is Part 3 of my Agentic Workflows series. Part 1 covers the workflow pattern, Part 2 walks through package audits.

You're reading an article about the workflow I used to write this article. I know. But stick with me—there's a genuinely useful pattern here.

The Problem

I spend hours in coding sessions with Claude Code. We solve problems, build features, learn things. Then the session ends and... it's gone. All that context, all those learnings, evaporated.

Meanwhile, I have a portfolio site with a blog that I never update because "writing takes too long."

The solution was obvious: make the agent write the articles.

The Article Builder Workflow

Like the package-audit workflow from Part 2, the article-builder lives at /workflows/article-builder.md. Here's how it works.

Step 1: Gather Source Material

At the end of a session (or during), I tell Claude:

"Document what we did today"

Claude then identifies:

**Session Topic:** What was the main goal?
**Key Accomplishments:** What got built/fixed/improved?
**Challenges:** What problems came up?
**Solutions:** How were they solved?
**Learnings:** What insights emerged?
**Code Highlights:** Notable code worth showing?

For this series, the source material was:

• Restructured CLAUDE.md from 300 → 100 lines
• Created /workflows pattern
• Built package-audit workflow
• Upgraded 9 packages via the workflow
• Created knowledge base system

Step 2: Choose an Angle

Not every session makes a good article. And the same session can produce different articles depending on the angle:

For this series, we chose Exploration—documenting a new pattern (agentic workflows) with practical examples.

One session became three articles:

1. The pattern itself (Part 1)
2. A specific implementation (Part 2)
3. The meta layer (Part 3—you're here)

Step 3: Structure the Draft

Every article follows a template:

# [Title]

**Hook:** 1-2 sentences stating the problem/opportunity

## The Challenge
What were you trying to do? Why does it matter?

## The Approach
High-level strategy before details.

## Implementation
Step-by-step with code snippets.

## What I Learned
Key takeaways—the "so what?"

## What's Next
Future improvements or related topics.

This structure works because it mirrors how developers think:

• Challenge = "I have this problem"
• Approach = "Here's my strategy"
• Implementation = "Here's the code"
• Learnings = "Here's what surprised me"

Step 4: Generate the Content

This is where the agent earns its keep. Claude drafts the full article including:

Code snippets with context:

// ❌ What didn't work
export const config = importedConfig

// ✅ What did
export const config = { api: { bodyParser: false } }

Before/after comparisons:

CLAUDE.md (before): 300+ lines, everything mixed
CLAUDE.md (after):  ~100 lines, core context only

Structured data:

The key is that Claude has full context from the session. It knows what we tried, what failed, what worked. That context becomes content.

Step 5: Save to TinaCMS

Using the article collection with full metadata:

# Creates the file
content/articles/agentic-workflows-part-3.md

Format includes SEO and series metadata:

---
title: "Article Title"
description: "SEO meta description"
publishedAt: 2026-02-07T00:00:00.000Z
series: "Agentic Workflows"
seriesOrder: 3
tags:
  - workflows
  - automation
featured: false
---

Content here...

The article is immediately available at /articles/agentic-workflows-part-3 on the site.

Why This Works

1. Context Is Already There

The hardest part of writing is gathering information. But in a coding session, the context already exists—we just finished living it. The agent has:

• The problem we solved
• The approaches we tried
• The code we wrote
• The errors we hit

Converting that to prose is mechanical.

2. Structure Removes Blank Page Syndrome

The template eliminates "where do I start?" Just fill in the sections:

• Challenge: ✓
• Approach: ✓
• Implementation: ✓
• Learnings: ✓

3. First Draft Is Free

The agent produces a complete first draft in minutes. It won't be perfect—I edited all three articles in this series—but it's 80% there. Editing is easier than writing from scratch.

4. Code Snippets Are Accurate

When I write articles manually, I often get code examples wrong (typos, outdated syntax). The agent pulls from actual code we just wrote. It's accurate by default.

The Recursive Bit

This article was written using the workflow it describes:

1. Source material: The article-builder workflow itself
2. Angle: Meta/exploration
3. Structure: Standard template
4. Content: Generated by Claude
5. Output: This file

The workflow documented itself. That's the point—once you have a workflow, it handles its own documentation.

Improvements I'm Considering

✅ Better Content Schema (Done!)

While writing this article, we built the article collection with full metadata:

{
  title: "Article Title",
  description: "SEO meta description",
  publishedAt: "2026-02-07",
  tags: ["workflows", "automation"],
  series: "Agentic Workflows",
  seriesOrder: 3,
  featured: false,
  body: "..."
}

This enables:

• Series navigation (Part 1 → Part 2 → Part 3)
• Tag-based filtering
• Featured articles on homepage
• Proper SEO metadata

Automated Publishing

Currently the workflow creates a draft. Future version could:

• Generate SEO metadata
• Create social media snippets
• Schedule publication
• Cross-post to Dev.to/Medium

Session Recording

What if the workflow ran continuously during sessions, capturing:

• Key decisions made
• Problems encountered
• Solutions found

Then at the end: "Generate article from session." The source material would already be structured.

The Workflow File

The complete workflow lives at /workflows/article-builder.md. It includes:

• Source material questions
• Angle selection guide
• Draft structure template
• Code snippet guidelines
• SEO checklist

When I finish a session and say "write an article about this," Claude reads the workflow and executes it. The article you're reading took about 10 minutes to draft.

What's Next

This series covered three workflows:

1. The pattern - Separating workflows from core docs
2. Package audits - A complete automation example
3. Article builder - Turning sessions into content

The /workflows/future.md file has more planned:

• google-analytics.md - GA4 setup and optimization
• seo-audit.md - Automated SEO checks
• workflow-explorer.md - Discovering what's possible

Each workflow makes the next one easier to build. The pattern compounds.

This article was written by Claude Code using /workflows/article-builder.md. Time from "draft Part 3" to complete: ~3 minutes. Editing took longer than writing.