tasks.md and VSCode todos ambiguity

[ppanchal-mobiz]

I know VSCode todos is an experimental feature, but I saw Den using it in the 'Let it cook' sessions. The problem I am facing with this is agent starts with tasks.md and creates todos to implement those tasks. As it continues, it keeps adding to the todo list the features that were not requested in tasks.md file. Then it starts implementing those features and digresses from the actual requirements. The agent also considers todos as task list and ignores marking tasks in the md file after completion.

[phebing]

I hit the same spot and I was wondering how it was originally intended.
I found the following in the speckit.implementation.prompt.md:

7. Progress tracking and error handling:
   ...
   - IMPORTANT For completed tasks, make sure to mark the task off as [X] in the tasks file.

Currently I am experimenting with the VSCode Todo List turned off and I am trying to get the agent to follow the above instruction.
I hope in that way I am able to start a new chat session from time to time, since in my experience (before spec-kit) it was better to keep the chat sessions small. Or is the idea behind this more like "keep the plan so small, that everything can be implemented in one session and then continue with the next spec"?

How are you dealing with tasks.md, progress and chat sessions?