task-status-sync

To keep tasks.md and NOTES.md synchronized, this Skill enforces atomic task sync by routing all status updates through centralized task-tracker commands, preventing manual edits from desyncing task state across files.

Manual edits are intercepted and blocked to prevent desynced task status. The system auto-converts attempted manual edits into valid task-tracker commands and logs the resulting errors or transitions for auditing.

Task-tracker validates status transitions by checking task IDs and enforcing valid state changes for in-progress tasks. It records any failures or invalid transitions across features to maintain consistent state and audit traceability.

Yes, you can use this atomic task sync workflow without external dependencies. It operates independently using internal scripts and references to manage task-tracker commands, requiring no additional packages or external libraries.

Task status updates fail to reflect in notes when unsynchronized manual edits bypass the task-tracker. Routing updates through the atomic sync commands ensures consistent state recording and prevents mismatched checkboxes and markers.

The best way to log task tracking errors is to route all updates through the task-tracker, which automatically records failures, validates task IDs, and captures status transition errors to ensure a consistent audit trail.