At the moment there’s no good way to hide existing tasks in the
tasks output (apart from using
null group but that doesn’t apply to tasks provided by the Java plugin). I’d introduce so-called life cycle tasks, tasks that users execute on a regular basis. Those tasks just depend on other tasks and don’t have a task action. For those tasks I’d add a specific group.
On top of that, writing some documentation and making it available to the team might help. The problem with documentation is though that you have to keep it in sync with the code.