skills.rest
obsfx
obsfxCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

task-sync

Sync Trekker task data with Codex session plans using Trekker as the source of truth.

Updated Mar 30, 2026
Search Tags:#workflow#planning#synchronization#codex#source-of-truth#task-sync#trekker
One-click install
npx skills add https://github.com/obsfx/trekker-codex --skill task-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-sync
Source: https://github.com/obsfx/trekker-codex/tree/main/skills/task-sync
Command: npx skills add https://github.com/obsfx/trekker-codex --skill task-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a durable, centralized record of work in Trekker while allowing Codex to plan interactively using a temporary mirror.

Core Features & Use Cases

  • Bidirectional syncing: Trekker is the source of truth; Codex session plans reflect Trekker updates.
  • Guardrails for consistency: Trekker updates must precede session plan refreshes; diverging data prioritizes Trekker.
  • Use cases include end-to-end task tracking for tasks, epics, comments, and dependencies within Trekker and Codex planning context.

Quick Start

Update Trekker first to establish the source of truth, then refresh the in-session plan to mirror the Trekker state.

Frequently Asked Questions about task-sync

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

FAQPage Schema
How do I sync task tracking data between planning sessions and a central source of truth?▼

To sync task tracking data, update the source of truth in Trekker first to establish the durable record, then refresh the in-session plan to mirror the Trekker state. This ensures planning sessions reflect consistent task, epic, and comment data.

What is the best way to maintain durable task memory across multiple Codex planning sessions?▼

Maintaining durable task memory across Codex sessions requires using Trekker as the centralized record. The session plan acts as a temporary mirror, guaranteeing context recovery and preventing long-term history loss for tasks and dependencies.

How does bidirectional synchronization handle diverging data between a session plan and Trekker?▼

Bidirectional synchronization handles diverging data by prioritizing Trekker as the source of truth. Guardrails enforce deterministic Trekker updates before any session plan refresh, ensuring consistency and preventing conflicting task states.

Can I use Codex for interactive task planning without losing track of long-term history?▼

Yes, you can use Codex for interactive task planning without losing track of long-term history. The synchronization process uses Trekker as the durable source of truth, preventing history loss while allowing temporary in-session planning.

Why does my session plan not reflect recent task and epic updates?▼

Your session plan may not reflect recent updates because Trekker must be updated first to establish the source of truth. If the in-session plan refresh occurs before Trekker is updated, the synchronization guardrails will block the mirror.

Does task synchronization work for tracking dependencies and comments or just basic tasks?▼

Task synchronization works for tracking dependencies, comments, and epics in addition to basic tasks. It coordinates end-to-end task tracking within Trekker and the Codex planning context to maintain full consistency.

Related Skills

Explore More Product & Management Skills→
obsfxobsfx

trekker

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

Community
Intermediate
horizontalsystemshorizontalsystems

aif-implement

Execute implementation tasks from active plans with Git-based progress tracking.

Official
Advanced
obsfxobsfx

task-agent

Coordinate Trekker task lifecycles with context recovery and progress updates.

Community
Advanced
pantheon-orgpantheon-org
1

subagent-driven-development

Dispatch fresh subagents for each task with two-stage reviews.

Official
Basic