A useful computer task should tell you what to do when you read it away from the original window. Vague labels such as “report,” “website,” or “email” force you to plan again before acting.
Start with a concrete verb and object
Write the smallest visible action: compare, draft, rename, export, send, or verify. Add the object and the project clue needed to distinguish it. “Compare the two homepage drafts” is more actionable than “homepage.” Avoid verbs such as “handle” or “work on” when they hide the real decision.
Name required material only when it helps entry: “Compare the two homepage drafts against the approved brief.” A stable link or file path belongs in notes when the task system supports it. Do not stuff a full project plan into the title.
Define a finish you can observe
State the result: “choose one and record the reason,” “export the signed PDF,” or “receive confirmation.” If completion depends on another person, separate your send action from the later follow-up. A task should not remain Doing merely because the larger project is unfinished.
Check whether it is really one action
If the task contains several independent verbs or produces several reviewable outputs, turn it into a project or a short ordered list. Keep preparatory steps only when they can block the action. Wallo lets you write to-dos under a goal and associate the goal with current windows, but it does not rewrite task text or infer which window contains the material.