newbie idea: is a project list necessary?

[JohnV474]

Hi all, newbie here. I've already become a big fan of the GTD program in the few months I've used it, and have found great delight in incorporating it into a 5x8 Moleskine notebook with tabs and a calendar insert. Along the way, I came up with the following idea:

Is a project list necessary? Before you decapitate me for heresy, hear me out. I'd like to get input on the idea.

I made a project list, and each list has an underlined keyword written in all caps. Example: Maintain TRUCK. My next action for that project may look like "@ Store: TRUCK--Buy oil for oil change." Upon completing that action, I then (immediately, upon completion), write the next Next Action into my list.

It seems that most projects are relatively straightforward a simple keyword reminder is enough to tell us all we need to know as far as what the goal is (e.g.: LAWN, TRUCK, DIET). For such projects, a projects list may be unnecessary. This may cause trouble for my RAM, but I don't know yet.

Some keywords are for bigger projects that have more moving parts. What of these, you ask? Well, the Project Support material takes care of that. The keyword MERGER (7 or LAWSUIT (84) indicates where to go for the Project Support list, so as each of the Next Actions for those are crossed off, I'd know to go to the Project Support page to scan for new Next Actions and immediately write them in.

I admit, I am just tossing the idea out there in theory because I haven't yet implemented it--I want to think it through more. The goal is to have as simple a system as possible, but no simpler.

What do you all think?

Thanks for your input
JohnV474