I’ve been using claude code for quite some time now, and recently I’ve found something that has been saving me a lot of grief, and it’s quite simple. {long planning session} Claude: OK, I have written the PRD document. It’s perfect. Me: Great. Now go make a fresh second pass searching for assumptions that you need to properly verify, gaps in the logic, and any general mistakes. It’s important we verify all assumptions and logic before commit to the plan. {thinking…} Claude: You were right to push back, I found 4 gaps, 3 unfounded assumptions, and 9 mistakes. That’s it. Just tell it to go back and do a second pass at the end of a long planning session and look for assumptions/gaps/mistakes. I just hit this again today where I had a PRD I had been working on for over an hour. It literally found 10+ items that needed to be reworked. This has cut down on the number of mistakes cropping up after the plan gets implemented dramatically. May seem simple, but the rules/hooks etc only go so far, and Claude will confidently tell you the plan is perfect when it’s not. submitted by /u/return_of_valensky
Originally posted by u/return_of_valensky on r/ClaudeCode
You must log in or # to comment.