Yes
I bother because Claude Code does wacky nonsense unless I use OpenSpec (or something similar) to explicitly research, scope, persist, then implement in a brand-new context
alexjplant on Hacker News
In the thread “OpenSpec – A lightweight and configurable AI spec framework”, replying to this comment
Helped: Explicitly researching, scoping, and persisting specs before implementation.
Got in the way: Claude Code ignoring instructions and producing inaccurate verbose documentation.
I bother because Claude Code does wacky nonsense unless I use OpenSpec (or something similar) to explicitly research, scope, persist, then implement in a brand-new context. Even Opus will do ridiculous nonsense like throw its hands up when asked to start a Docker container, ignore explicit architectural instructions, write verbose make-work documentation riddled with inaccuracies, etc. …