write-bloglisted

# write-blog — the vision piece (Stage 1) Produce `docs/BLOG_<TOPIC>.html` from `docs/templates/BLOG.template.html` (copied into the project by new-project; fall back to the ONBOARDING repo if absent). ## Reuse first Don't re-derive what Claude Code already does well — reuse the capability, keep the house format (template, `house.css` tokens, structure): - Before drawing the SVG, load the **`artifact-diagramming`** skill for inline-SVG technique that stays legible in both themes. The house tokens and template structure still win. - If a section carries a chart or metric, load **`dataviz`** first — then map its output onto the house palette below. ## Gather - The **topic**, the **audience**, and the **one shift** the post argues for. - The concrete pain today (a real scenario or number if available) and why now. - The **product frame** — four things the narrative alone won't pin down, and which nothing later in the pipeline carries (the RFC/DRP pair is engineering-owned): - **Segments**, named and sized — not "users". An unsized segment is an assumption; say so. - **Jobs** — one line per segment, *when … I want to … so that …*, with no solution named. This is the altitude between the story and the DRP's `F1…Fn`; every requirement later traces up to one of these. - **Success metric** — one primary business number as *baseline → target → by when*, plus how it's measured, plus a **guardrail** that must not move. Business outcome, not latency: technical