do-org.md

gistfile1.txt

---
description: Execute a specific org task
---

# Do the specified org task

Look in the org-mode file `~/org/work.org`, find the task with ID $1.

Read through the specific item, parent item, the previous and next TODO items,
and execute using the normal procedures the task with the selected id.

Before you analyze the problem, make sure the information in the task is
complete enough that you understand the issue.  If not, ask.

When you analyze the problem, you may need to present options to the user as
specified in the normal procedure. Add one other step: does the task need to be
broken down into several new tasks? This would only be true if the tasks would
take more than 30 minutes for a human to do and have noteworthy complexity on
their own. If so, propose the new subtasks to the user, and if they accept,
write them to the org file and stop there, and compress your context.

Leave it up to the user to mark it done, unless they specifically request you to
do so.

The name of the current project is taken from the `PROJECT` property, nested
based on the hierarchy. So, if the org structure looks like this:

> * Foo
>   :PROPERTIES:
>   :PROJECT: foo
>   :END:
> ** Bar and Baz
>   :PROPERTIES
>   :PROJECT: bar and baz
>   :END:
>    CLOCK: [2026-01-26 Mon 14:13]

Then the work task's project is called `foo/bar and baz`.