Anyone here using spec-driven AI development (OpenSpec, Superpowers, etc.) on real projects? I’ve tried a few of these workflows, but they seem to generate a ton of docs over time, and keeping everything updated feels like extra work. Lately I’ve been leaning toward: A project architecture doc A philosophy/conventions doc A few project rules Source code as the main source of truth For those using spec-driven workflows successfully, how do you avoid documentation bloat and spec drift? Curious what people have settled on in practice. submitted by /u/hossam7amdy
Originally posted by u/hossam7amdy on r/ClaudeCode
You must log in or # to comment.