LEMON AGENT Interactive example · from Start here: Write the brief
The finish line
The menu on my site breaks on phones. I want the agent to fix it without wrecking the design.
Which brief gives the agent the clearest finish line?
I redesigned the navigation: a slide-out menu, new icons, and I renamed two links for clarity.
It doesn’t break anymore, but it also doesn’t look like my site. I wanted a repair, not a redesign.
The goal sounds clear until the agent has to decide what “improve” means, which pages count, and how anyone will judge the result.
Done. I changed only the shared header styles. On small screens the three links wrap onto two readable lines, the build passes, and keyboard focus still reaches every link. The diff is one file.
Every part of “done” was something I could check myself. Nothing else moved.
Goal, scope, constraint, and proof are all visible. The agent can still solve the problem without silently redefining it.
I made the nav responsive and, following common practice, also normalized the spacing across the site.
The menu is fixed, but other pages shifted too. Is this done? I never said what done means, so neither of us knows.
It points in the right direction, but “best practices” is not an observable finish line. Name what must be true when the work is done.