Menu
Check Trekker for related tasks before creating a new one so work is extended instead of duplicated.
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.
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.
Translate natural-language tracking questions into Trekker queries for status, history, blockers, and related work.
| name | find-duplicates |
| description | Check Trekker for related tasks before creating a new one so work is extended instead of duplicated. |
Run this workflow before any new task creation.
trekker search "oauth" --type task,subtask --limit 5
trekker search "token" --type task,subtask --limit 5
If a matching or clearly related task exists, continue that thread instead of opening a duplicate.