/1 ▸ ask — the interview

Four batched rounds before a word is written: product, audience, problem, price, goal — then your voice (three words formality energy humor) — then design vibe from a five-menu, and the logo gate: optics are REQUIRED, waiver logged. Web round: domain, Cloudflare state, Search Console tag, GA4 id, competitors, channels.

artifacts ▸ facts block → voices and quirks captured, waivers explicit, ZERO copy produced yet — deliberate

uses your agent's native question UIunder 5 minutes

/2 ▸ position — one line that sells

Distills the facts into one-liner, ICP canvas, competitor wedge (names or optional research), 3 message pillars, keyword seeds, channel picks. Every later artifact in every channel must echo these pillars or it doesn't ship.

artifacts ▸ marketing/plan.md — one file every phase reads and resumes from

websearch optionalno research without permission

/3 ▸ landing — a page that exists

Delegates layout-movement to the frontend-design skill with the vibe you chose (this site: ASCII art, Astro multi-page, smooth view transitions). Landing keeps the head SEO-tight, wires the signup form to a real Cloudflare D1 binding, and degrades gracefully until deploy.

artifacts ▸ landing/index.html single-file · or an astro site/ when you ask

logo gate enforcedno fake testimonials

/4 ▸ seo — google legibility

Keyword map (1 primary, 3–5 secondary, alternatives phrases), robots.txt + sitemap.xml, JSON-LD schema matched per product type (SoftwareApplication · VideoGame · Product · Service), claims verified against page copy. No fabricated ratings — schema lies pickle rankings.

artifacts ▸ sitemap.xml robots.txt schema block in the head, keyword map in plan.md

schema.org validated

/5 ▸ deploy — stakes on the table

wrangler whoami → pages project create → deploy. GATE before the first deploy: you see the project name, file list, target URL. After first approval redeploys are automatic. D1 created and bound the same pass, schema applied, /api/signup live.

artifacts ▸ https://marketing-skill.pages.dev (or your domain) — page + database, free tier

first deploy: GATEDthen automatic

/6 ▸ verify — the google handshake

You paste the Search Console HTML tag from search.google.com (the flow is spelled out, 4 clicks). The pipeline injects it, redeploys, curls to confirm, then walks sitemap submission. Optional domain-wide DNS TXT route via the Cloudflare API — token stays env-only.

artifacts ▸ verified property + submitted sitemap (or a deferral logged with your reason)

account-bound: guided

/7 ▸ promo — the moving picture

HyperFrames composition from the pillars: hook → wedge → proof → CTA, 15–30s, 16:9 master + 9:16 cut. Music bed via media-use; voiceover by your chosen provider and voice (Cartesia pool first); narration ≤ 60 words. Poster, 6s GIF for READMEs, all rendered long-running in background.

artifacts ▸ promo/promo.mp4 · promo/promo.gif · promo/poster.png

delegates to hyperframesfallback: static set

/8 ▸ assets — six channels, one voice

X launch thread (hook discipline, UTMs) · Discord server skeleton + 90/10 etiquette · forum posts tuned per subreddit or HN Show format · LinkedIn hook-story-lesson · Product Hunt pack with exact specs (1270x760 gallery, 240 thumb, maker comment, reply kit) · ad creative images — generated, never spent.

artifacts ▸ marketing/assets/* · marketing/images/* — every link UTMed, grep-audited

image generationphase-jump friendly

/9 ▸ github — the repo facade

gh CLI: description, homepage, topics from the keyword map · README: existing ones win — the draft renders as a diff and ships on approval only · social preview card (1280x640) generated + upload guided (no API exists) · commit+push GATED.

artifacts ▸ polished repo + social card ready to upload

diff + approvenever force-push

phases ▸ the full pipeline