task-sync
Synchronize Trekker with Claude's built-in TodoWrite. Trekker is the source of truth.
What this skill does
# Task Synchronization: Trekker is Primary **CRITICAL: Trekker is the PRIMARY task tracker. TodoWrite is secondary.** Trekker persists across sessions in SQLite. TodoWrite only lives within a conversation. When they conflict, Trekker wins. ## The Rule ``` Trekker = Source of Truth (survives context resets) TodoWrite = Session Mirror (conversation-scoped only) ``` ## Automatic Sync Behavior ### When Starting a Session 1. Read Trekker state first: `trekker --toon task list --status todo,in_progress` 2. Populate TodoWrite from Trekker tasks 3. Never trust TodoWrite from previous sessions - always refresh from Trekker ### When Creating Tasks ``` 1. Create in Trekker FIRST: trekker task create -t "Title" -d "Description" 2. THEN mirror to TodoWrite: TaskCreate with same subject ``` ### When Updating Tasks ``` 1. Update Trekker FIRST: trekker task update TREK-n -s in_progress 2. THEN update TodoWrite: TaskUpdate for corresponding todo ``` ### When Completing Tasks ``` 1. Add summary comment to Trekker: trekker comment add TREK-n -a "claude" -c "Summary: ..." 2. Mark complete in Trekker: trekker task update TREK-n -s completed 3. Mark complete in TodoWrite: TaskUpdate status: completed ``` ## Priority Order | Scenario | Action | |----------|--------| | Trekker has task, TodoWrite doesn't | Add to TodoWrite | | TodoWrite has task, Trekker doesn't | Create in Trekker first | | Both have task, states differ | Trekker wins, update TodoWrite | | User creates via TodoWrite | Immediately create in Trekker | ## Why Trekker is Primary 1. **Persistence**: Survives context resets, TodoWrite doesn't 2. **Searchable**: `trekker search` finds past work 3. **Auditable**: `trekker history` shows change trail 4. **Dependencies**: Trekker tracks task relationships 5. **Multi-session**: Work continues across conversations ## Implementation Pattern Before ANY task operation, think: ``` 1. Is this in Trekker? → trekker task show <id> 2. Make change in Trekker FIRST 3. Mirror to TodoWrite AFTER 4. If conflict → Trekker wins ``` ## Anti-Patterns (DO NOT DO) - Creating in TodoWrite without Trekker - Trusting TodoWrite state from "previous session" (it's gone) - Updating TodoWrite but forgetting Trekker - Having tasks in TodoWrite that don't exist in Trekker
Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.