I came to this realization after seeing developers churn out 30 minute long reads of slop documentation. It's for the agent, and the human interface to it is through the agent. Over the last week the plans that Claude has been writing for issues have been largely a single massive unreadable paragraph of awkward sentences, but it's working, the implementations from it have been solid.
replythe key to avoiding slop in this context is to have it write inline documentation (e.g. jsdoc), so that you can quickly review if it matches the required implementation/interface
reply