From trekker
Synchronize Trekker with Claude's built-in TodoWrite. Trekker is the source of truth.
How this skill is triggered — by the user, by Claude, or both
Slash command
/trekker:task-syncThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**CRITICAL: Trekker is the PRIMARY task tracker. TodoWrite is secondary.**
CRITICAL: Trekker is the PRIMARY task tracker. TodoWrite is secondary.
Trekker persists across sessions in SQLite. TodoWrite only lives within a conversation. When they conflict, Trekker wins.
Trekker = Source of Truth (survives context resets)
TodoWrite = Session Mirror (conversation-scoped only)
trekker --toon task list --status todo,in_progress1. Create in Trekker FIRST:
trekker task create -t "Title" -d "Description"
2. THEN mirror to TodoWrite:
TaskCreate with same subject
1. Update Trekker FIRST:
trekker task update TREK-n -s in_progress
2. THEN update TodoWrite:
TaskUpdate for corresponding todo
1. Add summary comment to Trekker:
trekker comment add TREK-n -a "claude" -c "Summary: ..."
2. Mark complete in Trekker:
trekker task update TREK-n -s completed
3. Mark complete in TodoWrite:
TaskUpdate status: completed
| Scenario | Action |
|---|---|
| Trekker has task, TodoWrite doesn't | Add to TodoWrite |
| TodoWrite has task, Trekker doesn't | Create in Trekker first |
| Both have task, states differ | Trekker wins, update TodoWrite |
| User creates via TodoWrite | Immediately create in Trekker |
trekker search finds past worktrekker history shows change trailBefore ANY task operation, think:
1. Is this in Trekker? → trekker task show <id>
2. Make change in Trekker FIRST
3. Mirror to TodoWrite AFTER
4. If conflict → Trekker wins
npx claudepluginhub obsfx/trekker-claude-code --plugin trekkerCross-references Claude Tasks in backlog.org under Current WIP section when creating tasks, spawning subagents, or completing multi-step work. Requires existing backlog.org file.
Manages tasks via the taskwarrior CLI with annotations that reference markdown files, inline notes, and a Python script for opening task-related documents.
Executes eligible tasks from session task list, syncs against codebase/PR state to surface stales, and generates handovers. Use /task-run [--all] [--sync [--dry-run]] [--handover [query]].