task-status-sync

<quick_start> <enforcement_model> Intercept and convert manual edits to task-tracker commands:

1. Detect attempt: Monitor for Edit/Write tool usage on NOTES.md or tasks.md
2. Extract intent: Parse what change the user/Claude wants to make
3. Convert to command: Generate equivalent task-tracker command
4. Execute atomically: Run task-tracker to update both files simultaneously
5. Provide feedback: Explain the conversion and show the result

Example workflow:

User: "Mark T001 as completed"

❌ BLOCKED: Direct edit to tasks.md
✅ AUTO-CONVERTED: .spec-flow/scripts/bash/task-tracker.sh mark-done-with-notes -TaskId T001

Result:
- tasks.md: - [X] T001 Create database schema
- NOTES.md: ✅ T001: Create database schema - est (2025-11-19 10:30)

</enforcement_model>

<allowed_operations> ✅ Permitted (read-only):

• Read NOTES.md to understand progress
• Read tasks.md to see task list
• Read error-log.md to diagnose failures

✅ Permitted (through task-tracker):

• Mark tasks complete: mark-done-with-notes
• Mark tasks in progress: mark-in-progress
• Mark tasks failed: mark-failed
• Sync status: sync-status
• Get next task: next
• Get summary: summary
• Validate: validate

❌ Blocked (auto-converted):

• Direct Edit/Write to tasks.md
• Direct Edit/Write to NOTES.md
• Manual checkbox changes ([ ] → [X])
• Manual completion markers (✅ T001) </allowed_operations>

<task_tracker_commands> Available task-tracker.sh / task-tracker.ps1 actions:

# Get current status
.spec-flow/scripts/bash/task-tracker.sh status -Json

# Mark task completed with full details
.spec-flow/scripts/bash/task-tracker.sh mark-done-with-notes \
  -TaskId T001 \
  -Notes "Created Message model with validation" \
  -Evidence "pytest: 25/25 passing" \
  -Coverage "92% (+8%)" \
  -CommitHash "abc123" \
  -Duration "15min"

# Mark task in progress
.spec-flow/scripts/bash/task-tracker.sh mark-in-progress -TaskId T002

# Mark task failed
.spec-flow/scripts/bash/task-tracker.sh mark-failed \
  -TaskId T003 \
  -ErrorMessage "Tests failing: ImportError on MessageService"

# Sync tasks.md to NOTES.md (migration utility)
.spec-flow/scripts/bash/task-tracker.sh sync-status

# Get next available task
.spec-flow/scripts/bash/task-tracker.sh next -Json

# Get phase-wise summary
.spec-flow/scripts/bash/task-tracker.sh summary -Json

# Validate task file structure
.spec-flow/scripts/bash/task-tracker.sh validate -Json

See references/task-tracker-api.md for complete API reference. </task_tracker_commands> </quick_start>

Watch for these patterns that indicate task status updates:

Direct file edits:

• Edit(file_path: "*/tasks.md", ...)
• Edit(file_path: "*/NOTES.md", ...)
• Write(file_path: "*/tasks.md", ...)
• Write(file_path: "*/NOTES.md", ...)

Verbal indicators:

• "Mark T001 as complete"
• "Update task status for T002"
• "Task T003 is done"
• "Completed T004"
• "T005 failed"

Checkbox change patterns:

• old_string: "- [ ] T001" → new_string: "- [X] T001"
• Adding ✅ markers to NOTES.md manually </detection_phase>

<interception_phase> 2. Intercept and Block Manual Edits

When Edit/Write detected on tasks.md or NOTES.md:

⛔ MANUAL EDIT BLOCKED

File: specs/001-feature/tasks.md
Attempted change: Mark T001 as [X] completed

❌ Reason: Manual edits break atomic sync between tasks.md and NOTES.md

✅ Solution: Use task-tracker command instead

Auto-converting to:
  .spec-flow/scripts/bash/task-tracker.sh mark-done-with-notes -TaskId T001

This atomically updates:
  - tasks.md checkbox: - [X] T001
  - NOTES.md marker: ✅ T001: ... - est (2025-11-19 10:30)
  - Progress summary in tasks.md (if update-tasks-summary.ps1 exists)