When to Use

•When documenting significant project progress
•When sharing learnings publicly
•When the user wants to write about the development experience

Input

The user may specify:

•A time range: last week, since Monday, January
•A topic focus: the refactoring, new features, lessons learned
•Or just run it to analyze recent activity

Sources to Analyze

Gather context from multiple sources:

bash

# Recent commits
git log --oneline -30

# Recent decisions
head -100 .context/DECISIONS.md

# Recent learnings
head -100 .context/LEARNINGS.md

# Recent tasks completed
grep -A2 "\[x\]" .context/TASKS.md | head -50

# Journal entries (if available)
ls -la .context/journal/*.md 2>/dev/null | tail -10

Blog Post Structure

markdown

---
title: "Descriptive Title: What This Post Is About"
date: YYYY-MM-DD
author: [Ask user]
---

*Author / Date*

# Title

> Opening hook or question

[Introduction: Set the scene, why this matters]

## Section 1: The Context/Problem
[What situation led to this work]

## Section 2: What We Did
[Narrative of the work, with code examples]

## Section 3: What We Learned
[Key insights, gotchas, patterns discovered]

## Section 4: What's Next
[Future work, open questions]

Style Guidelines

•Personal voice: Use "I", "we", share the journey
•Show don't tell: Include actual code, commits, quotes
•Tables for comparisons: Before/after, patterns found
•Honest about failures: Include what went wrong and why
•Concrete examples: Reference specific files, commits, decisions

Process

•Gather sources (git, decisions, learnings, journals)
•Identify the narrative arc (what's the story?)
•Draft outline for user approval
•Write full draft
•Ask for revisions
•Save to docs/blog/YYYY-MM-DD-slug.md