update-task-board

To keep a task board in sync with project logs, this skill reads MIGRATION_LOG.md, DEBUG_LOG.md, and GIT_LOG.md to automatically classify and update task statuses. It cross-references commits and logs to move tasks accurately without manual edits.

You can automate task status updates from git commit history by running this skill after a work session. It analyzes GIT_LOG.md entries to categorize tasks into Completed, In Progress, or Next Steps, ensuring your task board reflects the latest code changes.

Evidence-based task board synchronization is the process of cross-referencing MIGRATION_LOG.md and DEBUG_LOG.md with GIT_LOG.md before moving tasks. It ensures an auditable, consistent progress record by preventing task updates without corresponding log evidence.

Yes, you can update TASK_BOARD.md without modifying CLAUDE.md or MIGRATION_LOG.md. This skill strictly enforces read-only access on those files while writing categorized progress updates exclusively to the task board.

Yes, this task board automation tool works with MIGRATION_LOG.md files by reading them alongside debug and git logs. It extracts task progress data from these logs to categorize items and maintain a clear project narrative.

The main limitation of using log files for task board updates is that the skill only reads MIGRATION_LOG.md, DEBUG_LOG.md, and GIT_LOG.md. If your project lacks these specific files or the logs are incomplete, task categorization will be limited.