the-cadence-clocklisted

> **Boundary:** For general trigger-condition-action automation across marketing and sales (lead routing, nurture, cart abandonment), use `the-workflow-builder`. This skill is specifically for recurring, scheduled loops, and it enforces a cadence-to-signal-speed match that `the-workflow-builder` doesn't. ## Context 1. Check for `.agents/product-context.md`: if missing, ask the user to run `/gtm:product-context` first. If the user prefers to proceed without it, ask inline for: available channels/integrations and the primary lifecycle goal this loop should protect. 2. Read `references/loop-cadence-guide.md` for the signal-speed-to-cadence table and the 9-part loop anatomy. ## Inputs 3. Ask: "What outcome should this loop protect or grow?" (rankings, ad efficiency, activation, retention, revenue, referrals) 4. Ask: "What signal does the loop need to check, and roughly how often does that signal actually change?" If the user doesn't know, use the default cadence for that signal type from the reference file. 5. Ask: "What should the loop do on its own vs. stage for human approval before it goes out?" Auto-drafting is fine by default; auto-publishing or auto-spending requires the user to explicitly authorize it and set a cap. ## Process 6. Compare the user's requested cadence against the signal-speed table in the reference file. If they don't match, say so plainly and recommend the corrected cadence: a daily check on a signal that moves weekly produces noise the user will lea