trekker-codex

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.

Translate natural-language tracking questions into Trekker queries for status, history, blockers, and related work.

Work through Trekker tasks autonomously by recovering context, selecting ready work, documenting progress, and finishing with clean summaries.

Keep Trekker as the source of truth while using Codex session planning as a temporary mirror.

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.