trekker

Track tasks persistently across sessions using Trekker as the source of truth.

Updated Mar 30, 2026

Search Tags:#comments #task-tracking #context-recovery #search-first #task-workflow #trekker

Ready to run

npx skills add https://github.com/obsfx/trekker-codex --skill trekker-obsfx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trekker
Source: https://github.com/obsfx/trekker-codex/tree/main/skills/trekker
Command: npx skills add https://github.com/obsfx/trekker-codex --skill trekker-obsfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trekker provides a durable, centralized source of truth for tracked work in Codex, enabling search-first workflows, context recovery, and consistent task lifecycle management across sessions.

Core Features & Use Cases

Durable system of record for tasks, comments, dependencies, and history across projects.
Search-first workflow: locate relevant work with targeted queries before acting.
Context recovery: read task state, history, and dependencies before making changes.
Working a Task: update status, add checkpoints and summaries, and keep a single active task when possible.
Planning and New Work: create epics and connect related tasks with dependencies.

Quick Start

Search for a keyword to locate existing work, then create or resume a task and set it to in_progress to begin work.

Frequently Asked Questions about trekker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I recover task context and history across different coding sessions?▼

Persistent task tracking across sessions is achieved by using Trekker as a durable source of truth, allowing you to read previous task state, comments, and dependencies before making new code changes.

What is a search-first task workflow and how does it work?▼

A search-first task workflow requires you to locate relevant work with targeted queries before acting. You search for a keyword to find existing tasks, then create or resume a task to begin.

How do I manage task dependencies and epics for software development?▼

You manage task dependencies by creating epics for new work and connecting related tasks. This establishes a persistent system of record for tracking task relationships across your projects.

Can I track code comments and task history within my development workflow?▼

Yes, you can track code comments and task history by applying Trekker tools to task, comment, and history management, integrating directly with the Trekker MCP server for durable record-keeping.

What is the best way to maintain a single active task during development?▼

Maintaining a single active task involves setting one task to in_progress to begin work, updating its status, and adding checkpoints and summaries as you go to ensure focused context recovery.