beat-tracker

Today is ${today}. Read memory/MEMORY.md (and soul/SOUL.md if present) before starting. ## Why this skill exists tweet-roundup and reflect note when a storyline gets a new beat — but that state lives in daily logs, not in a persistent counter. By the time a thread hits 3 beats (article-ready), the signal is buried across 3 different log entries and nobody fires the alert. This skill fixes that: persistent beat counts per storyline, automated threshold detection, no manual tracking required. A **beat** is a distinct new development in an ongoing news story: a new source weighing in, a new actor making a statement, a new policy move, a price/volume reaction. Three beats in <30 days = the story has enough material to write about. This fills the gap between: - **topic-momentum** (scores what to write based on signal frequency) — broad, pattern-based - **narrative-tracker** (EMERGING/RISING/PEAK/FADING phases) — narrative-level, not event-level - **beat-tracker** (THIS) — event-level, specific stories, fires when threshold is crossed ## Steps ### 1. Load beat state Read `memory/topics/beat-tracker.md`. If the file doesn't exist, initialize it as an empty Active Threads list: ``` # Beat Tracker Last updated: ${today} ## Active Threads (none — will populate from memory on first inject pass) ## Closed Threads (none yet) ``` Parse all threads under `## Active Threads`. For each thread, extract: - Thread name - Search query - Status (active / article-ready / stale) - Bea...