@dexhorthy I have tried multiple approaches for researching the codebase (including the generic one from your repo) and given it researches a backend feature that spans 10+ files it always misses some important details
@badlogicgames I mean you shouldn't blindly trust it with writing anything, to me, tests are not less important than production code. Maybe add a phase where CC comments out a line of code to see the test fail to verify it's working in the first place 🤷♂️
@badlogicgames And then I tell it to work on task by task (each task in separate subagent with clear context, where I tell it to pass the original plan md and the tasks json file) and tell it to proceed on next pending task
@badlogicgames What I do is I have a comprehensive md plan containing what code changes should be done tests etc, and I tell CC to format that plan into a template file tasks-template.json (that I created originally using Claude Task Master, and it is working quite good)
don't start your next project without reading/watching all the nuggets from this article
https://t.co/j0W8UfLMRa
Thanks @steipete for the collection.
Learnt a few tricks for sure (logging centrally and tracing)
@badlogicgames Then I let it analyze complexity and create subtasks, after it's done I let it execute using a simple prompt using jq (thx for that), after each task it stops and waits for me to verify, after all is done it commits, I wipe the context (back to start) and repeat
@badlogicgames Then I tell it to create a very detailed plan on how to implement the changes in the spec and I iterate with it to also include unit tests and BDDs. After few iterations when I am okay with everything I use taskmaster to create a plan it's a JSON file as well