Writing tasks is an art form in itself. Write too little, and you risk forgetting something or not fully understanding your upcoming workload. Write too many, and you'll find yourself overwhelmed, spending more time organizing than actually accomplishing tasks.

Therefore, a task should be thoughtfully defined to cover a manageable chunk of work. It should be substantial enough to justify putting it on your list but not so broad that you never get the satisfaction of checking it off. Sometimes, a task may consist of a couple of mini-actions that require careful consideration to ensure nothing is forgotten. In Fugoya, we've introduced subtasks to address precisely this scenario. Subtasks in Fugoya are essentially text lines without additional metadata, allowing you to maintain a flat hierarchy with one level. If you need additional information like priority, project, or due date, you should consider breaking the task into regular tasks.

This approach is crucial to avoid losing sight of your tasks. Sub-sub-subtasks tend to be the things that slip through the cracks and get forgotten. If you find yourself wanting to create a subtask of a subtask, it's best to ask yourself: How can I break this down into regular tasks instead? If the task at hand is so extensive that it can't be subdivided, then you're dealing with a project, not a task. In that case, you know what to do!