Lazy project definitions

[Bernt Hansen <bernt@norang.ca>]

Hi,

I've been using the definition that all LEVEL 2 tasks are projects for a
long time.  Recently I tried switching to explicitly marked projects
using a :project: tag (or PROJECT keyword) but I really dislike having
to manually mark projects in my task lists.

A project for me is basically any LEVEL 2 task that has one or more
subtasks.

I would like to define my org stuck projects as LEVEL=2/!-DONE-CANCELLED
with an added skipping function that does not consider level 2 tasks if
they have no children.  I can't figure out how to make this work in the
org-agenda-custom-commands using the skipping function but I think it
should be possible.

My goal here is to add 2 custom agenda commands:
  p - show me projects (level 2 tasks not completed with children)
  o - show me other (non-project) tasks (level 2 tasks without children)

I don't want the 'o' - other tasks listed in my stuck projects view
since these are really one-task items and are not a project by my
simplistic definition above.

I've been using everything as a project that is defined at LEVEL 2 for
ages and that works really well for me -- except I want to stop spending
any time dealing with simple (non-project) tasks when looking for next
tasks and stuck projects.  Sure I could manually mark my tasks as
projects but I don't think that should really be necessary for what I
want to do here... and if it could just say a LEVEL 2 task with children
is a project it would work automagically for me without any additional
input.

For simple non-project tasks I don't need to mark them as NEXT to make
them unstuck -- they aren't projects to begin with and I can have
a convenient way to view all of these simple non-project commands in the
agenda using the 'o' custom command.

Is there a way to this?

Thanks,
Bernt