Menu
Suggest or manage Trekker tracking when the user talks about bugs, features, backlog items, or work that should survive this session.
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.
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.
Translate natural-language tracking questions into Trekker queries for status, history, blockers, and related work.
| name | issue-tracking |
| description | Suggest or manage Trekker tracking when the user talks about bugs, features, backlog items, or work that should survive this session. |
Use this skill when the conversation shifts from discussion into tracked work.
trekker search "pagination" --type task,subtask --limit 5
trekker search "cursor" --type task,subtask --limit 5
Use single keywords. Trekker search is full-text, not semantic.
trekker task create -t "Fix pagination cursor regression" -d "Investigate duplicate results in cursor pagination under filtered list view." -p 1
trekker comment add TREK-14 -a "codex" -c "Checkpoint: reproduced duplicate results when sorting by updated_at."
If Trekker is not initialized in the current workspace, ask before running trekker init.