From 372b68e74b1356d45ffbd67746d64cc2b71b0d6f Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 25 Feb 2026 21:53:26 +0200 Subject: update prompts --- prompts/skills/project-taskwarrior/2-start-task.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'prompts/skills/project-taskwarrior/2-start-task.md') diff --git a/prompts/skills/project-taskwarrior/2-start-task.md b/prompts/skills/project-taskwarrior/2-start-task.md index ec34f25..6b44811 100644 --- a/prompts/skills/project-taskwarrior/2-start-task.md +++ b/prompts/skills/project-taskwarrior/2-start-task.md @@ -11,7 +11,7 @@ Work on each new task **must begin with a fresh context** — e.g. a new session When you begin working on a task, **always mark it as started in Taskwarrior** so current work is visible: ```bash -task start +task uuid: start ``` Do this as soon as you start work on the task. @@ -19,5 +19,6 @@ Do this as soon as you start work on the task. ## Conventions - Start each new task with a fresh context; rely on the task’s description and annotations for all required context. -- Run `task start` when you start working on the task, not only when listing or completing. +- Run `task uuid: start` when you start working on the task, not only when listing or completing. - Do not start a second task for the same project while one is already started and not done, unless the user explicitly asks. +- When a task is selected via the review/overview step, use the stored UUID (for example, `uuid:`) for subsequent `start` operations, not a freshly-looked-up numeric ID from a new report. -- cgit v1.2.3