Planning/design/estimating checklists

[Keith Clarke]

Hi folks,
I want to get smarter at solving issues earlier in the design stage, as my coding skills (or lack thereof) makes the repeated, radical reworking of code - each time I realise I've forgotten something basic - both unproductive and a real bore.
Are there any basic 'Do/Don't/Consider' checklists to use when planning/design/estimating a new application, stack, card, script. library, etc. 
Best,
Keith..