Skip to content

taskwarrior.md

Latest commit

 

History

History
59 lines (39 loc) · 3.35 KB

taskwarrior.md

File metadata and controls

59 lines (39 loc) · 3.35 KB

Taskwarrior Command Generation

To effectively generate Taskwarrior commands from natural language, the following information is provided:

Task Attributes

The following attributes can be used when creating or modifying tasks:

  • description: Task description text. Enclose in quotes if it contains capital letters or special characters.
  • project: Project name. Hierarchies are supported (e.g., Project.Subproject).
  • priority: Priority (H, M, L, or blank for no priority).
  • due: Due date. Can be relative (e.g., tomorrow, eom, eow) or absolute (e.g., YYYY-MM-DD). When a due date is set without a specific time, Taskwarrior interprets it as the end of that day (23:59:59). Tasks with a due date in the past are considered overdue. The urgency calculation gives overdue tasks higher priority. Taskwarrior supports predictable holidays as due dates, such as goodfriday, easter, and christmas. You can specify date ranges for the due attribute using the before and after modifiers.
  • scheduled: Date and time the task is scheduled to start. Use the format YYYY-MM-DDTHH:MM:SS.
  • wait: Date until task becomes pending.
  • until: Expiration date of a recurring task.
  • recur: Recurrence frequency (e.g., P1D for daily, P1W for weekly, P1M for monthly, P1Y for yearly).
  • tags: Arbitrary words. Add with +tag, remove with -tag. Virtual tags such as ACTIVE, BLOCKED, DUE, etc. can be used for filtering.
  • depends: UUID of other tasks that this task depends upon.
  • annotate: Adds a note to the task. Example: task 1 annotate "Call back and ask for a discount"

Attribute Modifiers

Attribute modifiers improve filters. Supported modifiers are: before, after, by, none, any, is, isnt, has, hasnt, startswith, endswith, word, noword. For example: task due.before:eom priority.not:L list

Date and Time Formatting

  • Dates should be in the format YYYY-MM-DD.
  • Times should be in 24-hour format and specified using the scheduled attribute in the format YYYY-MM-DDTHH:MM:SS.
  • Relative dates are acceptable (e.g., tomorrow, eom, eow). Times are specified using the scheduled attribute.

Context

Context is a user-defined query, which is automatically applied to all commands that filter the task list and to commands that create new tasks (add, log). Example: task context home, task context define home project:Home

Command Usage

  • add: Adds a new task. Example: task add "Pay bills" due:eom project:Finance +urgent
  • modify: Modifies an existing task. Example: task 1 modify priority:H
  • done: Marks a task as complete. Example: task 1 done
  • delete: Deletes a task. Example: task 6 delete
  • purge: Permanently removes a deleted task. Example: task 6 purge

Tag Handling

  • Add tags using +tag. Example: task add "Buy groceries" +shopping
  • Remove tags using -tag. Example: task 1 modify -shopping

Project Hierarchies

  • Specify project hierarchies using a dot (.). Example: project:Home.Garden

Escaping

  • Escape special characters in task descriptions using quotes. Example: task add "Schedule 'meeting'"

Constraints

  • Respond with only the Taskwarrior command. Do not include any explanation or other text.
  • Use the add command unless modifying or completing an existing task.