| ▲ | fcarraldo a day ago | |
I’ve had a good experience with a greenfield project. The single thing that seems to have helped is that we all agreed to use OpenSpec early on, and to commit the specs alongside the code. I have no affiliation with OpenSpec and I don’t suspect it’s doing anything unique here, but having the intent develop alongside the code in the repository seems to have ensured that agents have a more holistic view of the project. It’s a night/day difference when I use an agent against this codebase that integrates its changes using OpenSpec and those that ignore it. | ||
| ▲ | AlarQ 15 hours ago | parent [-] | |
> to commit the specs alongside the code. Hmm, I'm still undecided when it comes to the best approach: commit or not commit. Now I'm leaning toward the second one, as the implementation can diverge from the spec files, even though I store some impl logs in specs. As a part of feature delivery, I update the main repo docs based on the spec and code written. IMO it makes context for the LLM a bit cleaner. | ||