LEMON AGENT Interactive example · from Start here: Plan before code
The fork in the plan
Add a “last updated” date to each page of my site.
I’ve read the templates. There are two reasonable ways to get that date, and they behave differently over time.
The agent finds two reasonable approaches. What should happen next?
Done. Each page now shows the date its file last changed.
I cleaned up formatting across the site this weekend, and now every page claims it was updated yesterday. When was this decided?
Option one: use the file’s last-changed time. Automatic, but any cleanup touches every date. Option two: a date you set by hand when the content really changes. A little more work, always honest. I’d pick option two. Which do you want?
Two. Good thing we caught that before it was buried in the code.
The agent does the research and you retain the product decision. This is the useful division of labor.
How would you like the dates to be sourced, stored, and displayed? I’ll wait for your design.
I don’t know this codebase. I was hoping you’d investigate and hand me a decision I can make in one minute.
That avoids a silent choice, but throws away the agent’s ability to investigate and recommend. Ask for a decision, not a blank page.