Multi-task plans

Big requests become step-by-step plans — pages get batched, navigation is set up first, and you watch progress per step.

Ask for several things at once and Genesis doesn't cram them into one blurry build — it makes a plan and executes it step by step.

How to trigger it

Any compound request:

• "build pages for Home, Pricing, and Checkout"
• "make a landing with a product catalog and add my GTM"
• "create an About page, a blog, and a contact form"

What you'll see

A step list with live progress:

✓ Step 1/4: Wiring site navigation
⏳ Step 2/4: Build 3 pages: Home, Pricing, Checkout
   Step 3/4: Product catalog
   Step 4/4: Tracking (GTM)

Sometimes Genesis shows you the plan first and asks "Go ahead / Change something" — answer and it runs. On a brand-new multi-page build it may also ask whether the first page should be your home page or its own route.

Smart things it does automatically

• Navigation first. A multi-page build starts by scaffolding your navbar and footer with real links to every planned page — so nothing ships with dead navigation.
• Pages are built together, not one-by-one. One architectural pass over the whole set means a consistent theme, shared components, and working cross-page links.
• Specialist steps stay specialist. Something like a product catalog or tracking setup inside a big request becomes its own dedicated step — it doesn't get lost in the page building.
• A final integration check sweeps the result for unwired buttons, dead links, and missing glue between the steps.

Notes

• Steps run one at a time; if one fails, the rest still run — the summary tells you what completed and what didn't. Nothing already built is lost.
• Plans cap at 15 steps; truly huge asks are better split across a couple of messages.