Planning reliability in task tools

Aperta
  • Qualcosa non va?
#409 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
csharp, openapi
Ambito
backend-api-design, devtools

Direzione di ricerca

The issue says parts 2 and 4 remain, while part 3 overlaps #412 and #415; it also says the work is done after the code move to nevridge/TaskFlow#398. Read the transferred issue and those related issues before choosing any work. Confirm which parts are still open, then coordinate the three-way decision for part 3; completion means the remaining accepted parts meet their listed criteria and the required docs and tool-surface test are synced.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Groomed 2026-10-30 — ready for implementation.

Status 2026-11-04: trimmed when the issue was transferred to nevridge/TaskFlow. It is done after the code move (nevridge/TaskFlow#398). Part 1 (planned day in update_task) shipped as nevridge/taskflow-assistant#28 and part 5 (in progress) as nevridge/taskflow-assistant#26, so only parts 2, 3 and 4 remain. Part 3 overlaps #412 item 1 and #415 (report moved tasks); decide the three together. The original text of parts 1 and 5 is in the issue history.

Original Description

Context

Found while using Claude as a daily assistant via this MCP on 2026-10-12/13.

2. Echo the planned day in create_tasks results

Some results show planned, others don't, so a task created without a day looks the same as one created with a day. Task nevridge/taskflow-assistant#13 missed today's list this way. Always report the planned day (or "not planned").

3. Report when other tasks move

Planning a task on tomorrow's journal can silently move other tasks forward (see nevridge/TaskFlow#240, related to #233 and nevridge/taskflow-assistant#1). Once the API reports it, surface it in the tool result. Until then, consider a note in the tool description.

4. Backlog definition and view

Definition: status todo with no planned day. Add a backlog view (or filter) to list_tasks and describe it in the tool descriptions to avoid confusion with draft.

Dependencies

  • Part 3 is unblocked: nevridge/TaskFlow#245 fixed the original silent move, and #249 added movedCount and movedTaskItemIds to the journal-entry create response.

Suggested build order: parts 2 and 4, then part 3 together with nevridge/TaskFlow#412.

User Story

As a person planning my work through the assistant, I want to see each created task's planned day (or "not planned"), to be told when other tasks were moved, and to list my backlog, so that tasks don't silently miss the day's list and I can trust what the assistant reports about my plan.

Acceptance Criteria

Part 2: planned day always reported

  • Given create_tasks succeeds, when results are returned, then every created task's line shows "planned " or "not planned", including tasks created without journalDate.

Part 3: moved tasks

  • Given the MCP creates a journal entry (through the journal resolver's ensure path, for example in set_journal_todos) and the response has movedCount > 0, when the tool result is built, then it lists the ids in movedTaskItemIds and the count.
  • Given movedCount is 0, when the tool result is built, then no moved-tasks text appears.

Part 4: backlog view

  • Given tasks with various statuses and planned days, when list_tasks is called with view backlog, then only tasks with status todo and no planned day are returned.
  • Given project or priority filters, when they are combined with backlog, then both apply.
  • Given no view is specified, when list_tasks runs, then the default is still open, and open does not change.
  • Given the tool descriptions, when they are read, then they define backlog as "todo, no planned day" and say it is different from draft (a stored status, not a view).

Sync

  • Given these changes, when the story is done, then the tool-surface test (including the view list), the plugin and chat docs, the agent file and the README are updated together, as CLAUDE.md requires.

Edge Cases

  • Un-planning. Nothing here says how to clear a planned day, which would return the task to backlog. This story does not add it.
  • Overlapping views. An overdue, unplanned todo task appears in both backlog and overdue.
  • Wording. "Backlog" versus "draft", and "Draft" used as a verb in the weekly_review description, can confuse readers.
  • Moved-task visibility. Moves only occur when today's entry is created, which depends on the timezone offset sent. The todos endpoint may not return movedTaskItemIds, so moves there may be invisible.

Out of Scope

  • Un-planning or clearing a planned day.
  • A draft view, or any change to what open contains.
  • Showing the planned day in the concise format of list_tasks and other tools beyond create_tasks results.
  • Reworking the get_journal versus list_tasks planning-source disagreement.
  • Reporting moves from the todos endpoint response.
Lingua principale
C#
Stelle
1
Fork
0
Merge medio
2h 2m
PR unite (30g)
98

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nevridge/TaskFlow

Tutte le issue di nevridge/TaskFlow

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.