Build code with agents while keeping a working understanding

A developer describes a workflow where the agent interviews them on ambiguities, makes the minor decisions, generates explainers and quizzes, and runs verifiers in the coding loop.

What They Did: Before building, the agent interviews the developer on ambiguities in the spec (a /grill-me style prompt). The developer makes decisions on stack and architecture only for differentiating parts and leaves minor details and commodity subsystems like login to the agent. A skill generates interactive explainers with quizzes. Linters, type checkers, pre-commit hooks, tests, formal-method traces and a headless-browser design verifier keep the agent checking its own work.
How It Went: The developer says this keeps them out of the 2am fix-and-break loop while still building understanding. No measurements are given, and they note other engineers are split on whether understanding the code matters.
Worth Knowing: The design verifier turns spec requirements into mechanical rules checked against DOM measurements in a headless browser, which the author says was impractical before agents.

Try it yourself with custom-built or unnamed agent

I want to build [feature or project] in this codebase, and I want to stay able to understand everything you write. Before coding, interview me about any ambiguities in the plan, one question at a time, and make the minor decisions yourself, listing them for me. After each major piece, write a short explainer of how it works and give me a 3-question quiz on it, then run the tests or checks before moving on.

Read the original ↗