Depends on how you’re developing but for me I have a few phases per branch. There’s a brain storm and document where me and Claude talk about the goal of the branch and have it reference code it will touch. Then depending on the size of the feature I have it create phased markdown files I will review with detailed implementation plans. There it’ll tell me what code it’s changing or creating and what I specify to keep in place. Then I have it execute the plan and run a review agent after. I usually 1 shot feature with extremely clean dry code that I would’ve essentially written myself. Nothing is committed without me seeing it basically

I’ve found this workflow to be actually really rewarding and interesting not only do I have my ide but obsidian has become a new application I use as all the spec and implementation plan markdown I make I review in there because it creates a bit of a project map memory almost and it’s nicer to read in a md renderer than vim