obsfx
10 verified skills
find-duplicates
Check Trekker for related tasks before creating a new one so work is extended instead of duplicated.
testing
issue-tracking
Suggest or manage Trekker tracking when the user talks about bugs, features, backlog items, or work that should survive this session.
tools
smart-query
Translate natural-language tracking questions into Trekker queries for status, history, blockers, and related work.
databases
start-task
Start tracked work the right way: search first, restore task context, check dependencies, then mark the task in progress.
testing
task-sync
Keep Trekker as the source of truth while using Codex session planning as a temporary mirror.
development
planning
Plan multi-step work in Trekker before implementation. Use epics, tasks, and dependencies so work survives session resets.
testing
complete-task
Close Trekker work cleanly by reviewing context, adding a summary comment, marking the task complete, and surfacing the next ready item.
testing
search
Search Trekker first to recover context before creating, starting, or updating tracked work.
tools
task-agent
Work through Trekker tasks autonomously by recovering context, selecting ready work, documenting progress, and finishing with clean summaries.
documentation
trekker
Use Trekker as the persistent source of truth for tracked work in Codex. Search first, restore context, work one task at a time, and close tasks with summary comments.
development