I did a search through the site and found some similar questions with some answers that aren't quite what I'm after. What I'm looking for is if there is a recommended way to note that a task is dependent on another task or requires completion of another task before it is started.
A few things I have been thinking of is marking the "prerequisite" task as high priority, or as another thread mentioned, putting the prerequisite task as a next action, while any dependent tasks should not be on next actions. Also, I was thinking about putting all dependent tasks in a project, where the project is the task that is the prerequisite for the group of tasks.
The problem with the ideas I have been brainstorming is that they don't really address the actual issue I'm having. I have a bit of difficulty planning and thinking things through, so I need to be able to have some sort of note in tasks that shows which tasks need to be completed before starting it, because otherwise I'll start the task, then realize that I can't complete it, and my productivity mojo for the day will be shot.
I was thinking of just making a tag for the prerequisite so that tasks can have multiple dependencies, but that kind of goes against the whole idea of tags. It is the best thing I can come up with though. Ideally, it would be nice to have something that works with Doit.im, but I don't really see that happening unless I use tags. I guess I've kind of answered my own question typing the question out, but I'm not entirely satisfied with my own answer. Does anybody have anything else they've used successfully?
To be honest though, this doesn't necessarily have to comply 100% with GTD, I'm more after any solutions that anybody else has used successfully to deal with dependency issues in their productivity workflow, as I don't follow GTD religiously in the first place. I hope this wasn't a super confusing question, and I greatly appreciate any answers.