cadence-plannerlisted

Take a pile of drafts (or a content goal) and turn it into a **sensible, human-looking posting rhythm** — how many a week, which days, what times, spread so it never reads as a bot — then create the loop(s). **You do the drafting** when drafting is needed; capx never generates content, it only ships (every post clears the casserole guardrail at send). User's material or target, if any: "$ARGUMENTS" If you're not connected to X yet, run the **connect** skill first — loops can't be created without it. Follow these steps: 1. **Get the material.** Two cases. (a) The user hands you a **backlog of drafts** — those are theirs; use them as-is (only polish if asked). (b) They give only a **goal or theme** — then *you* write the posts, grounded in real things (their actual work, product, or experience). Never fabricate features, numbers, or outcomes. Count how many posts you have — that number drives everything below. 2. **Pick a sustainable rate.** A healthy build-in-public rhythm is **~3–5 posts/week**. Resist dumping the whole backlog in one week — more than roughly one a day reads as spam, and the guard blocks near-duplicates and low-effort filler anyway. Compute the **runway**: posts ÷ per-week = how many weeks the queue lasts. Name the tradeoff out loud (post more often → run dry sooner). 3. **Spread it so it's not robotic.** Pick days *across* the week rather than clustered, and **vary the time-of-day** instead of firing the same minute every day. Ancho