marketing-loops

Pick a loop from the catalog that matches your goal, tune its cadence to how fast the underlying signal changes, define its state handling and stop condition, then schedule it via cron, Claude Code primitives like CronCreate, or a manual weekly run.

Signal-driven tasks like ranking-drop watches, ad-fatigue checks, churn-signal monitoring, dunning recovery, content-decay refreshes, and competitor tracking work well. Strategy, positioning, and creative direction should not be looped because they require human judgment.

By default no. Drafting and staging run autonomously, but spending money, sending messages, and publishing require a human checkpoint unless you explicitly authorize them with hard spend caps and an allowlist of eligible accounts or campaigns.

Match cadence to signal speed: rankings and competitor changes weekly, ad fatigue every 2-3 days, churn signals daily, and content decay monthly. Over-frequent loops generate noise and train you to ignore the output.

The loop is missing state and idempotency handling. Persist a cursor or watermark, dedupe keys for items already acted on, and per-entity cooldown windows in a state file so re-runs skip previously handled work.

Skip loops when the work is strategy or creative direction, when the signal is too sparse to be significant, or when nobody acts on the output. A loop whose output goes unread is a vanity loop and should be deleted.