The agent explains, then checks against the spec
iamwil lets the agent finish its questions before it codes, and he has it write explainers with quizzes. A check opens a headless browser and measures the DOM against the spec rules.
Done with Valgfri agentModerate
What was done
On 19 October 2026 iamwil writes that he changed how he works once agents started writing the code. He uses an interview, including /grill-me, so the agent asks about what is ambiguous. He makes the stack and architecture choices where the product is different. The agent may take ordinary parts, such as login, and small details. When he does not understand a subsystem, he asks for a visual explainer as markdown or HTML, with a quiz afterwards. A design check turns requirements in the spec into rules, opens a headless browser and compares DOM measurements. Linters, type checks and pre-commit hooks stay fixed. For harder state he asks for a formal proof, then a trace, then unit tests that follow the trace. The point, he writes, is to avoid being up at 2 asking the agent to fix what it just broke. He does not name the product.
How it went
He describes the workflow as what lets the agent check itself. He does not give a count of defects caught.
Worth knowing
The product is not named. The comment does not show a named page where the DOM check passed. The quiz explainer is a skill he says he has, not an attached example.
How to do it
- Ask the agent to question what is ambiguous in [task] before it codes.
- Ask for an explainer with a quiz for [subsystem] if you do not understand it.
- Read the spec rules and the diff yourself before anything is deployed.
Try it with Valgfri agent
With [tool], ask me what is ambiguous in [task] before you write code. Make an explainer with a quiz for [subsystem]. Do not deploy until I say yes.
Replace text in brackets with your own.
Done when. You have answered the questions, and nothing has been deployed unless you said yes.
Safety rule. The agent does not deploy. You make the architecture choices where the product differs, and you read the checks.
Read the original
Read the original · comment by iamwil on Hacker News ·