Repository navigation
[Decompose] Tracking of User Stories and Tasks concluded #56
Description
When agents carry out implementations based on User Stories and Tasks, they sometimes lose track of what has been implemented because they forget to mark the tasks as complete.
Observed behavior
Agent forgets to mark tasks as complete after implementation and try to implement again until realize that tasks has already implemented.
Desired behavior
After implementation, mark the implemented tasks as complete.
Activity
fedeoliv commentedon Oct 16, 2026
Implementation verified, pending merge.
Added a durable Completion Checkpoint before another task or commit, including when commits and PRs are deferred. Local-only tasks persist verified checkboxes, GitHub records verified implementation separately from merge, and ADO uses supported nonterminal states or active-state evidence. Resume checks inspect existing evidence before state changes to avoid reimplementation. Workers return evidence and pending commit scopes, while the coordinator persists/readbacks completion before committing in normal and streamlined modes.
Validation:
git diff --checkandnpm --prefix docs run buildpassed. Independent lifecycle reviews verified local-only completion, GitHub resume without a PR, ADO Tasks without Resolved, commit deferral, and drift handling. Changed Markdown has no new lint diagnostics compared with HEAD.Branch:
feature/56-durable-task-completion.Commit:
e30aaa0a90c81361773cfd0e570edd18b5aad00f.PR: #81.
Changes are committed and pushed. Merge the dependency first: #80. Retarget this PR to main if GitHub has not done so automatically. The issue remains open until merge.