Learn / For your team

How to brief your developer on agent readiness

Agent readiness briefs badly as a general concern and well as four specific tickets: structured data in the served markup, a variant picker that works without a pointer, an add to cart that is a real form, and a checkout that survives a cold session. Each has an observable symptom you can attach as evidence, which is what turns it from a discussion into work.

This briefs badly as a general concern and well as four specific tickets. The difference is not presentation, it is that the four things have observable symptoms and the general concern does not.

Gather the evidence first

Half an hour with scripts disabled produces everything you need. Open three product pages, one bestseller, one with several variants and one out of stock, and record what is missing on each. Then walk checkout from a cold session on a narrow viewport and record every point where you had to do something.

See how to audit your store for agent readiness in an afternoon.

The four tickets

  1. Structured data in the served markup. "With JavaScript disabled, these URLs have no price or availability. Emit price, availability, variant data and an identifier server side."
  2. Variant picker. "Options are not present in the markup / require a hover. Use real form controls with options in the served HTML and availability per option."
  3. Add to cart. "The control is a click handler with no form. Wrap it in a form posting the variant id and quantity to the existing endpoint, and keep the script intercepting the submit."
  4. Checkout cold. "From a fresh session on a narrow viewport, these steps blocked the path to payment: [list]. Remove or bypass them for a guest."

Say why, briefly

One sentence is enough: agents read the served markup and do not run our scripts, so anything that only exists after render does not exist for them. Developers get this immediately, and it is also the accessibility argument, which makes it easier to prioritise.

What not to ask for

Do not ask for a protocol integration or an MCP server. Neither is the work for a store on a hosted platform, and including them makes a small, well defined request look like a research project. See do you need to adopt a commerce protocol at all.

Ask for the guard too

A fifth, smaller ticket: a test that fetches a product page without scripts and asserts price, availability and variant options are present. It stops all four of the above from coming back.

Questions

Why not just send the whole checklist?

Because a checklist reads as a project and gets scheduled rather than done. Four tickets with observable symptoms read as bugs, which is closer to what they are.

What evidence should I attach?

What you observed with scripts disabled, on which URLs. "The price is absent from this URL with JavaScript off" is a reproducible defect. "We need to be AI ready" is not.

What should I not ask for?

Anything framed as an integration or a protocol. That is almost never the work for a store on a hosted platform, and asking for it makes the real request look larger and more speculative than it is.

Scan your store

How to brief your developer on agent readiness · Ottom