Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
Stephan
@stephancill
Anyone here building large projects using Claude code? My current approach is to 1. write a context doc describing the problem and solution with product requirements 2. produce a technical specification via a back and forth with a thinking model based on the requirements doc 3. Get a thinking model to develop a daily plan for an engineer 4. Give Claude code the requirements, spec, and plan and tell it to implement one day and write do a write up in a standup doc when it’s done. 5. When it’s done I review the changes and ask it for revisions until I’m satisfied 6. After that I start another Claude session to implement the next day with all the docs and also include the relevant standup docs. Rinse and repeat This seems to work really well. Curious if others are doing it differently and getting better results Shoutout @jc4p for sharing this approach
8 replies
0 recast
45 reactions
meatballs
@meatballs
I also throw bdd into the mix and have a set of specs and tests in gherkin
1 reply
0 recast
1 reaction
Stephan
@stephancill
Sorry what’s bdd in this context?
2 replies
0 recast
0 reaction
emo.eth
@emo.eth
behavior driven development extension of test driven development if you’ve used a test framework that groups test contexts in describe() and it() blocks, you’ve done bdd
1 reply
0 recast
2 reactions
meatballs
@meatballs
When I've used it myself, it's been great but it adds another layer that has to be maintained. AI tools make that maintenance trivial and so the technique itself becomes powerful.
0 reply
0 recast
0 reaction
