marketing featureshowinstallfaq ★ star

how ▸ end to end

One command expands into nine phases with check-ins between each. Diamonds are the gates; everything else runs in your agent, on your machine.

pipeline diagram
mermaid diagram of the /marketing pipeline: trigger command, SKILL.md router, 9 phases, delegations to frontend-design and HyperFrames, external services Cloudflare GSC GitHub GA4, artifacts
three invocation forms

▸ /marketing — full run: interview → all 9 phases, pause-and-confirm after each

▸ /marketing promo — one phase only; reads marketing/plan.md, skips the interview, jumps in

▸ after the first full run — /marketing posts regenerates channel assets whenever content evolves, no interview again

resume state

marketing/plan.md is the single source of truth: facts block, voice profile, pillars, keyword map, channel picks — plus a status table the pipeline writes back to after every phase. Kill the run mid-way? Re-run tomorrow, it resumes.

a day in the pipeline — morning: interview (5 min) · verify the one-liner · pages build while you grab coffee · deploy one "yes" away · video renders in background · by evening: thread, forum posts, PH pack, README diff ready to ship.