From a4f6be9ce441c6771e0f1bb9e03fce65f0a2d5b5 Mon Sep 17 00:00:00 2001 From: Anrg-init Date: Sun, 8 Feb 2026 01:53:11 +0530 Subject: [PATCH] Clarify task interpretation rules for ambiguous user input --- productivity/skills/task-management/SKILL.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/productivity/skills/task-management/SKILL.md b/productivity/skills/task-management/SKILL.md index e2323c6..21e0153 100644 --- a/productivity/skills/task-management/SKILL.md +++ b/productivity/skills/task-management/SKILL.md @@ -71,6 +71,15 @@ Task format: - Read the Waiting On section - Note how long each item has been waiting +## Task Interpretation Rules + +When interpreting user input related to tasks: + +- If a single message contains multiple distinct tasks, split them into separate task entries. +- Preserve the user’s original wording for task titles whenever possible. +- If task intent or a due date is ambiguous, ask a clarifying question before writing to `TASKS.md`. +- Do not infer deadlines, priorities, or assignees unless explicitly stated by the user. + ## Conventions - **Bold** the task title for scannability