Menu
Keep Trekker as the source of truth while using Codex session planning as a temporary mirror.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Start tracked work the right way: search first, restore task context, check dependencies, then mark the task in progress.
Close Trekker work cleanly by reviewing context, adding a summary comment, marking the task complete, and surfacing the next ready item.
Check Trekker for related tasks before creating a new one so work is extended instead of duplicated.
Suggest or manage Trekker tracking when the user talks about bugs, features, backlog items, or work that should survive this session.
Plan multi-step work in Trekker before implementation. Use epics, tasks, and dependencies so work survives session resets.
Search Trekker first to recover context before creating, starting, or updating tracked work.
| name | task-sync |
| description | Keep Trekker as the source of truth while using Codex session planning as a temporary mirror. |
Use this skill when the user wants both durable tracking and an in-session checklist.
Trekker = persistent record
update_plan = session-local mirror
When they diverge, Trekker wins.
update_plan only after Trekker is correct.update_plan to preserve long-term task history, blockers, or summaries.trekker task update TREK-8 -s in_progress
trekker comment add TREK-8 -a "codex" -c "Checkpoint: narrowed the issue to the pagination query in src/services/list.ts."
Then update the session plan so the current conversation reflects the tracked task. Do not skip the Trekker update.