I just use beads or Github issues. Plan/spec first, split it into issues.
Then reset context and implement each task one by one. Nothing gets forgotten.
I just use beads or Github issues. Plan/spec first, split it into issues.
Then reset context and implement each task one by one. Nothing gets forgotten.
A key part of this is making sure bite sized issues reference any related holistic concerns like code quality, testing, documentation style, commit strategy, git workflow etc.
In my experience you have to refer to the relevant docs on things explicitly in every single issue for it to work well.