[trcf23]

Wow thanks for sharing! Could you explain how you made the specs? Did you already know pretty much everything you wanted to cover before hand? Was one CC session enough to go through it?

In my experience, trying to make a plan/specs that really match what I want often ends in a struggle with Claude trying to regress to the mean.

Also it’s so easy to write code that I always have tons of ideas I end up implementing that diverge from the original plan…

[Leftium]

- No, I did not know everything I wanted to cover beforehand. Claude helps me brainstorm, research, and elaborate on my ideas. The spec is a living document that I occasionally check in: https://github.com/Leftium/rift-transcription/commits/main/s...

- It was definitely not one CC session. In fact, this spec is a spin-off of several other specs on several other branches/projects.

- I've actually experienced quite the opposite: I suggest an idea for the spec and Claude says "great idea!" Then I change my mind and go in the opposite direction: "great idea!" again. Once in a while, I have to argue with Claude to get my idea implemented (like adding dependencies to parse into a proper AST instead of regex.)

- One tip: it's very useful to explain the "why" to Claude vs the "what." In fact, if you just explain the why/problem without a specific solution, Claude's suggestions may surprise you!

[MarleTangible]

The what-why switch is quite useful, because it also helps you avoid Claude's "great idea!" responses as well.