weekly-issue

name	weekly-issue
description	Draft this week's Ian's List newsletter issue from real work signals — personal research findings, Hacker News, and GitHub — then render it and stage it as a prod draft with a test send to Ian only. Use when Ian asks to draft the weekly issue, run the Saturday pipeline, or prep the newsletter.

Weekly Issue Pipeline

Turn a week of real work into a drafted newsletter issue. The output is a draft in Ian's inbox, not a task on his list.

Editorial contract (non-negotiable)

The issue is a 1-3-5, roughly a 5-minute read, with one main ad slot and a handful of classifieds:

1. One main thing — the single most impactful share of the week. Ian writes this section himself as a human. The pipeline's job is to propose 2–3 candidate angles with supporting material, never to ghost-write it.
2. Three cool things — each backed by an agent-created demo or insight plus Ian's personal comment. A featured tool must HELP the reader and be shown in real use: actually build something small with it (cut a real video with the video tool, run the real audit against ian.is), ideally written up as a post on ian.is so traffic/SEO/backlinks accrue there. Never a bare link. The demos are the differentiator.
3. Five quick tips — from Ian's real AI chats this week. Each gets a tagline plus a description with enough context to be genuinely helpful, and must name a concrete benefit (faster, better output, security, time saved). Run an obviousness filter: kill anything a regular AI user already knows.

Hard rules:

• The five-criteria test. Every item needs: concrete problem, failed standard approach, non-obvious move, reusable recipe, evidence it worked. If a tip could be written without having done the work, kill it. Fewer, stronger items beat coverage — a 2-item issue that passes beats a 9-item issue that doesn't. Calibration examples are the "good" verdicts in notes/newsletter/feedback.jsonl (read them fresh each run; they accumulate). png-to-svg is one example that passes, not a template.