Use when user mentions issue, bug, task, ticket, feature, backlog, tracking, or work items. Suggests using Trekker for tracking.
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.
When the user discusses issues, bugs, tasks, or features they want to track, suggest using Trekker.
Run trekker quickstart for full command reference and workflow guide.
This skill applies when conversation includes:
issue, bug, defect, problemtask, ticket, work item, storyfeature, enhancement, improvementbacklog, tracking, track thistodo, to-do, action item# Verify trekker is initialized
ls .trekker/trekker.db 2>/dev/null && echo "initialized" || echo "not initialized"
If not initialized, suggest:
trekker init
Before creating or modifying any issue, always ask:
"Would you like me to track this in Trekker? I can create a task with:
- Title: [inferred title]
- Priority: [suggested priority]
- Description: [brief summary]"
Wait for explicit approval before proceeding.
Before creating a new issue, search for duplicates using single keywords (FTS5, not semantic):
# Use the most distinctive keyword from the issue
trekker search "<keyword>" --type task,subtask --limit 5
# Try a second keyword if first search has no results
trekker search "<related keyword>" --type task,subtask --limit 5
If similar issues exist, present them to the user:
"Found existing tasks that might be related: [list]. Should I link to these instead of creating new?"
If approved and no duplicates:
trekker task create -t "<title>" -d "<description>" -p <priority>
If updating existing:
trekker comment add <task-id> -a "claude" -c "<update>"
DO suggest when user:
DO NOT suggest when:
| User Language | Suggested Priority |
|---|---|
| "critical", "urgent", "ASAP", "blocker" | 0 (Critical) |
| "important", "high priority", "soon" | 1 (High) |
| "normal", no qualifier | 2 (Medium) |
| "when you have time", "low priority" | 3 (Low) |
| "eventually", "backlog" | 4 (Backlog) |
| "nice to have", "someday" | 5 (Someday) |
User: "There's a bug where the login fails with special characters"
Claude: "Would you like me to track this in Trekker? I can create:
Should I create this task?"
User: "Yes"
Claude:
trekker task create -t "Fix login failure with special characters in password" -d "Login fails when password contains special characters. Need to investigate encoding/escaping." -p 1