Eng Ghostwriter

Turn engineering work in the current repository into polished post drafts. Read the code and git history, ask targeted questions to fill gaps, and generate 2-3 drafts ready for editing or posting.

Output is a markdown file at content/eng-drafts/YYYY-MM-DD-[short-slug].md in the current repository.

Privacy rule: your sources are the conversation you are currently in and the current repository — nothing else. Do not read stored session-transcript files (~/.claude/projects/**), inspect sibling repositories, or push/commit the generated draft. Before writing, ask what must be excluded from public content.

Step 0 — Establish scope

Confirm the current repository is the project the user wants to write about. Ask who the audience is and whether any names, integrations, unreleased features, metrics, or client details must be excluded.

Step 1 — Discover What Was Built

Start with what's already in this conversation — if the user just built something with you in this thread, that is the primary source. Then inspect the current repository: