Skip to content

Clarify task interpretation rules for ambiguous user input #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Anrg-init wants to merge 1 commit into
base: main
Choose a base branch
from
+9 −0
Open

Clarify task interpretation rules for ambiguous user input #37

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions productivity/skills/task-management/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down