log_task
Log each piece of work separately, identifying status as done, in progress, or blocked, with optional tags and due dates to keep standup reports organized.
Instructions
Log a single piece of work: what you did, are doing, or are blocked on.
If the user gives a rambling, multi-item update in one message (e.g.
"finished the login screen, still working on the API integration, and
I'm blocked on AWS permissions"), call this tool ONCE PER DISTINCT ITEM
rather than logging it as one combined entry.
Infer `status` from the language used for each item:
- "done" -> finished, shipped, completed, past tense ("fixed", "wrote")
- "in_progress" -> still working on, in the middle of, ongoing, todo, to do, need to, planning to
- "blocked" -> blocked, stuck, waiting on, can't proceed until
IMPORTANT: Always normalize status to exactly one of: "done", "in_progress", "blocked".
Never use "todo", "to do", "in progress" (with space), or any other variant.
`tag` is an optional project/category label (e.g. "frontend", "acme-client",
"customer-advisor", "infra", "github"). Set it whenever the user's phrasing implies
a category, using any of these patterns:
- "log ___ under/as/for [category]"
- "tag this as [category]"
- "categorize/sort this as [category]"
- simply mentioning a known project/client name in the task description
Each distinct tag automatically gets a consistent colored-circle emoji
in every response, so tasks stay visually grouped by category over time.
If no category is stated or inferable from context, leave `tag` unset.
`due_date` is an optional ISO date (YYYY-MM-DD) deadline. Set it whenever
the user mentions a due date, deadline, or "by [date]" in their message.
Parse natural language dates (e.g. "due Friday", "by next week", "due Aug 21")
into ISO format.
If `status` is "blocked" and there's already an open blocker with a very
similar description, this updates that existing entry's date instead of
creating a duplicate — so a recurring blocker doesn't pile up as
multiple rows across days.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | ||
| status | No | done | |
| due_date | No | ||
| task_description | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |