How do you tackle "TODO Driven Development"? The sort of thing I am thinking of is a noon-urgent / do-when-time type refinement to the code, not something that must be done before it will work at all.
I tend to put a comment in the code which is syntactically incorrect that thus will break, so that when I run the code (e.g. to create a stored procedure / trigger) I have to comment out the TODO. That way I at least get reminded that there are still unfinished items in the code every time I execute the code - because it is tedious to have to comment them out. When I check-in the code to revision control system I remove any such commenting-out's (I use a unique marker so I can globally replace easily), and that way anything commented-out gets reactivated, and has to be thought about again when the code is next executed.
It occurs to me that:
The comments are still in the SProcs, after creating, so I could report on them
I could replace / augment the TODO comments with SProc calls - then real executing code would "log" all the embedded TODOs. That might help me with a "popularity" Stats report / graph
Other suggestions please?