[sealjam]

Your comment inspired me to try all 3 tools in combination, and at first glance it seems like a very nice solution; certainly more effective than my current manual method. A quick question for you though, if you don't mind: do you use taskwarrior just as a backend for taskwiki or do you use it in its own right aswell?

I like the idea of just being able to add todo items quickly from a shell without opening the task list but I imagine those items would not be reflected in my taskwiki list without some kind of taskwarrior hook.

[lambdasue]

On the contrary, taskwiki provides two-way sync, so they will show up in your taskwiki lists. The feature is called Viewport, and it's a header enhanced with a taskwarrior filter:

Say you have all your work tasks tagged with 'work'. Then your taskwiki file might look like this

    This file contains all the work-relevant information.
    
    === My work tasks | +work ==
    * [ ] Implement feature X

After saving that file, you will see the task in taskwarrior as well (with the tag assigned).

If you subsequently do: $ task add +work Test feature X

The next time you open the taskwiki file, it will look like this(syncing happens when you open the file):

    This file contains all the work-relevant information.
    
    === My work tasks | +work ==
    * [ ] Implement feature X
    * [ ] Test feature X

The power of this setup is that you can add a task on your phone (i.e. when the idea hits you in the public transport), have it automatically sync over the taskserver to your desktop, and when you open the taskwiki file relevant to the project, the task is there!

[sealjam]

aha! I was missing the requirement for a project/viewport combination for two way sync.

Many thanks for the above information and the initial recommendation. This setup seems to be exactly what I've been looking for for quite some time.