Original Reddit post

There have been quite a few skills and discussions focused on clarifying specs before Claude Code starts coding (e.g., by asking Socratic questions). I’ve found a better approach: dispatch agents to investigate features, propose multiple solutions, and have reviewers rate and challenge those solutions — then compile everything into a clean HTML report. Sometimes Claude comes up with better solutions than what I originally had in mind. Without this collaborative brainstorming process, those better solutions would never get implemented, because I’d just be dictating the codebase design. Another benefit of having agents propose solutions in a report is that I can start a fresh session to implement them without losing technical details. The report contains enough context that Claude can implement everything from scratch without issues. In short, I think the key to building a good codebase is to collaborate with Claude as a team — having real discussions rather than crafting a perfectly clear plan of what’s already in my head and simply executing it submitted by /u/kalesh_kate

Originally posted by u/kalesh_kate on r/ClaudeCode