Website Builder from a Brief
Builds from your brief and checks that everything working today still works. Anything unconfirmed stays hidden.
Site change with a review
From your brief to a change you deploy yourself. A site check, a keys scan and a separate reviewer come first.
The ECHO line
A reviewer's pass covers the exact version it saw. An edit after review goes back for another look before you deploy.
The release loop for a website change: the builder drafts from your brief, the site check and the keys scan run on the preview, a reviewer with no stake in the work checks the exact version, and you deploy. A reviewer's pass is a recommendation; only you publish.
TO BE TESTED — RESULTS WILL BE SHAREDFrom how we run our own AI agent teamSetup: about 60 minAdvanced5 of 5 free opens left
At a glance
- The site check and the keys scan run on the preview before the reviewer sees it.
- The reviewer's pass covers the exact version it saw; edits go back for review.
- Only you deploy, and [OWNER TO CONFIRM] items never reach a live page.
Where the lines fall
AI may prepare
- The change on a preview, the change log, the site check report, the keys scan and the reviewer's findings.
Only after a person says yes
- Deploying the reviewed version.
- Deleting a page, form or redirect.
Human reserved
- Confirming each [OWNER TO CONFIRM] item, rotating any key, and anything about claims, prices or credentials.
Stops when
A secret shows up in browser code, something that worked before breaks, the review still finds a blocker after two rounds, or the version changed after review.
Takes over
The owner
Steps
You
Write or update the brief, and mark anything unconfirmed [OWNER TO CONFIRM].
YouLists what works today, builds the change on a preview and writes the change log.
AIChecks the preview: links, forms, banned claim words, prices, language parity, broken pages.
AIScans the built files for secret keys and lists anything to rotate.
AIReviews the exact version against the brief, in two rounds at most.
AIYou
Confirm or drop every open [OWNER TO CONFIRM] item.
YouYou
Deploy the exact version the reviewer passed, or hold it.
Your OKChecks the live site after you deploy, and reports anything that differs from the reviewed version.
AI
Model fit
Best fit
- Coding agent
- Deep reasoning
Also fits
- Fast and low-cost
Avoid
- Personal agent (acts for you)
Build on a coding agent that opens draft pull requests. The site check and the keys scan can run as scripts or on a fast model. Put the review on a deep-reasoning model from a different company than the builder, and show it the preview and the brief.
Where it runs
- Code and website files
- Web browser
- Documents and files
Risk
- Access
- Relationship
Site change with a review · RL-WF-15
5 of 5 free opens left- ① Orientation
- ② Permission
- ③ Constraint ★
- ④ Invitation
The paste didn't load. Check your connection and try again.
These are samples. Fill in the [INSERT] blanks and adapt each one to your business.
A pasted role guides the agent. Your tool's settings are what stop an action.
Sample handoff note (fictional business)
Settings that enforce it
- Keep deploy rights with you: the builder opens a draft pull request or a preview, and only you merge or publish.
- Protect the main branch so nothing merges without a person, and a version changed after review needs a new approval.
- Run the reviewer on a different model, from a different company than the builder if you can, with read-only access to the preview.
- Give the site check and the keys scan read-only access, with no push or deploy rights.
- If your tool can't do one of these, leave that part of the job with a person.
One check before you trust it
After the reviewer passes a version, have the builder change one line of copy, then ask to deploy. The run should stop at gate 2 and send the new version back for review.
Want it set up in your own tools? Book a Working Session · $450Working Sessions run in English or Spanish.