Menu
Search Trekker first to recover context before creating, starting, or updating tracked work.
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.
Translate natural-language tracking questions into Trekker queries for status, history, blockers, and related work.
| name | search |
| description | Search Trekker first to recover context before creating, starting, or updating tracked work. |
Trekker search is the primary context recovery tool.
trekker search "auth"
trekker search "migration"
trekker search "release"
trekker search "fix the authentication bug in login"
trekker search "what changed in the release flow"
If search results are thin, broaden with a second keyword and inspect nearby tasks via comments and history.