Anthropic said Sonnet 5 was intended for agentic workflows, and now I believe them. Sonnet <5 was not good at orchestrating subagents and following processes. I had to use opus for what seems like simple work of routing requests to subagents. Out of curiosity, I tried /implement-sprint (long-running code changes) with Sonnet 5 and it was flawless. No more, “Let’s stop here.” Aren’t getting, “Step 3 is done, do you want to continue to step 4?” Just completing the process and recovering when things go wrong. One thing I noticed is it doesn’t seem much faster than Opus on the same thinking levels anymore. But that’s just going on feel. I haven’t tested. [Edit] This repo is pretty old and I’ve optimized a lot of this stuff, but the general pattern still holds /arch-design -> /arch-review (usually multiple) -> /create-sprint -> /implement-sprint -> /fold-pending. The process works really well for me. Once a project’s architecture is set, adding features is usually really smooth. https://github.com/leogodin217/leos_claude_starter submitted by /u/leogodin217
Originally posted by u/leogodin217 on r/ClaudeCode
You must log in or # to comment.