task-status-sync

To prevent manual edits from desynchronizing task files, intercept direct file modifications and convert them into atomic task-tracker commands. This ensures tasks.md and NOTES.md are always updated together, preventing data loss and maintaining project integrity.

Enforce atomic task status updates by using a dedicated bash script like task-tracker.sh to execute transitions. Instead of manually editing task files, run commands that validate TDD compliance and parallel task safety while atomically updating tracking files.

Yes, you can use bash scripting to validate TDD compliance and parallel task safety during task transitions. The script intercepts status update commands, checking validation rules before atomically modifying the task tracking files to maintain project integrity.

The best way to mark a task as complete without causing file inconsistencies is using a command like task-tracker.sh mark-done-with-notes. This atomically updates task tracking files and logs completion details, bypassing error-prone manual edits.

Yes, you need to adhere to specific file formats for task tracking, such as maintaining tasks.md and NOTES.md. The atomic update mechanism requires strict file format compliance to validate task transitions and synchronize status changes correctly.

You should use a task-tracker command instead of directly editing task files because manual edits bypass validation rules for TDD compliance and parallel task safety. The command ensures atomic updates, preventing the inconsistencies and data loss associated with unvalidated file modifications.