article-queue

Today is ${today}. Read `memory/MEMORY.md` before starting. ## Why this skill exists Three skills generate article signals, none of them feed the article skill: - **topic-momentum** — scores uncovered angles vs narrative frequency - **beat-tracker** — tracks multi-beat storylines, alerts at 3 beats (article-ready) - **narrative-tracker** — labels narratives EMERGING / RISING / PEAK / FADING The article skill reads `memory/MEMORY.md` but picks topics from scratch every run. This means a 3-beat thread can sit article-ready for days while the article skill writes about something else. This skill closes that gap: runs weekly (after topic-momentum finishes), synthesizes all three signal sources, and writes a ranked queue to `memory/topics/article-queue.md`. The article skill will encounter the queue via MEMORY.md naturally. A queue entry is only as good as its urgency. Priority order: 1. **Beat-ready** (≥3 beats) — the story is cooked. Write it now. 2. **Warming up** (2 beats, most recent beat ≤5 days ago) — one beat away. 3. **topic-momentum picks** — scored by gap score, freshness, soul-fit. 4. **Narrative-tracker RISING/EMERGING** not yet written about. ## Steps ### 1. Load beat-tracker state Read `memory/topics/beat-tracker.md`. If it doesn't exist, skip beat signals (log a note). Parse all active threads. For each thread extract: - Thread name - Status (active / article-ready / stale) - Beat count - Most recent beat date - Latest beat summary Flag threads with `statu...