Use Trekker to plan and track multi-step tasks BEFORE starting implementation.
From trekkernpx claudepluginhub obsfx/trekker-claude-code --plugin trekkerThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Before starting any multi-step task, break it down in Trekker FIRST.
This ensures:
Use this workflow when:
# ALWAYS search first - previous work may exist trekker search "<what you're about to do>"
For features with multiple tasks:
trekker epic create -t "Feature: User Authentication" \
-d "JWT-based auth with login, registration, and session management"
Create atomic, completable tasks:
# Each task should be independently completable
trekker task create -t "Create User model with email/password" \
-d "Define User schema with bcrypt password hashing" \
-e EPIC-1 -p 1
trekker task create -t "Implement login endpoint" \
-d "POST /api/auth/login - validate credentials, return JWT" \
-e EPIC-1 -p 1
trekker task create -t "Implement registration endpoint" \
-d "POST /api/auth/register - create user, hash password" \
-e EPIC-1 -p 1
Make execution order explicit:
# Login depends on User model
trekker dep add TREK-2 TREK-1
# Registration depends on User model
trekker dep add TREK-3 TREK-1
After Trekker is set up, create matching todos:
TaskCreate for each Trekker task
Set blockedBy relationships matching Trekker deps
BAD: "Fix bug"
GOOD: "Fix null pointer in UserService.getById when user not found"
BAD: "Add feature"
GOOD: "Add email validation to registration form"
Every task MUST answer:
trekker dep list TREK-ntrekker task update TREK-n -s in_progressIf context is about to reset:
trekker comment add TREK-n -a "claude" -c "Checkpoint:
Done: [what's complete]
Next: [what's remaining]
Files: [modified files]
State: [any important context]"
User: "Add user authentication to the API"
# 1. Search first trekker search "authentication"
trekker search "login"
# 2. Create epic
trekker epic create -t "User Authentication System" \
-d "JWT-based auth with login, registration, password reset"
# 3. Create tasks
trekker task create -t "Design auth database schema" \
-d "Users table, refresh tokens, password reset tokens" -e EPIC-1 -p 0
trekker task create -t "Implement User model" \
-d "Drizzle schema with bcrypt password hashing" -e EPIC-1 -p 1
trekker task create -t "Create auth middleware" \
-d "JWT verification middleware for protected routes" -e EPIC-1 -p 1
trekker task create -t "Implement login endpoint" \
-d "POST /auth/login - credential validation, JWT generation" -e EPIC-1 -p 1
trekker task create -t "Implement registration endpoint" \
-d "POST /auth/register - user creation with validation" -e EPIC-1 -p 1
trekker task create -t "Add auth tests" \
-d "Unit tests for auth service, integration tests for endpoints" -e EPIC-1 -p 2
# 4. Set dependencies
trekker dep add TREK-2 TREK-1 # Model depends on schema
trekker dep add TREK-3 TREK-2 # Middleware depends on model
trekker dep add TREK-4 TREK-2 # Login depends on model
trekker dep add TREK-5 TREK-2 # Register depends on model
trekker dep add TREK-6 TREK-4 # Tests depend on login
trekker dep add TREK-6 TREK-5 # Tests depend on register
# 5. Mirror to TodoWrite with same structure
Plan in Trekker FIRST, then execute. Never start coding multi-step work without a Trekker plan.