marketing-loops

Pick a loop from the catalog matching 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 cadence.

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.

By default no. Spend, send, and publish actions are Tier-2 gated actions requiring human approval unless you explicitly authorize them with hard spend caps, per-run change limits, and an allowlist of eligible accounts or campaigns.

Skip loops for strategy, positioning, and creative direction, which require human judgment. Also avoid loops when the signal is too sparse to be significant or when nobody acts on the output, since those become vanity loops.

Persist state between runs using a cursor or watermark, a dedupe set of handled items, per-entity cooldown windows, and in-flight guards. Store this in a state file such as .agents/loops/<loop-name>.json and append a run log each execution.

Marketing ideas are one-off tactics to try once, while loops operationalize the tactics worth repeating on a schedule. Loops add cadence, self-checks, state, and stop conditions so the work continues reliably without manual re-triggering.