not all tasks are done after running /implement

[eibrahim]

I noticed that the tasks.md for my spec doesn't have all the tasks marked as done and some tasks are not even done after running /implement... what's the best practice here? run /implement again? or is there a better approach?

[Gustav-CW]

I tried just re-running tasks until all of them were finished. I can't tell for sure yet if it was the best approach. I suggest you do the same thing and post your findings.

[bicatu]

What do you mean by re-running tasks? Is it by saying TXX all over again?

[Gustav-CW]

I just ran /implement (nothing else in the prompt) several times after each other.

[bicatu]

I assume it detected that there were no missing implementations and just marked the tasks as done. Was it?

[Gustav-CW]

No, my agent stopped after like a third of the tasks were done. But when I re-ran /implement it just saw which tasks were marked as done and continued down the list.

[craig-blowfield]

The is the same behaviour I have experienced.

It does a few tasks for each /implement call, so I have had to run it at least ten times so far and still going.

Even when providing a comment such as

/implement tasks until they are all complete seemed to make no difference.

Is this expected behaviour? For example, to allow user steering between tasks