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

issue-tracking

Suggest Trekker task creation and updates from bug and feature discussions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage Trekker tracked work surfacing from user conversations about bugs, features, backlog items, or work that should survive this session.

Core Features & Use Cases

  • Duplicate checks: search for duplicates before creating new work to avoid fragmentation.
  • Safe creation & updates: prompt before creating or updating tasks and update existing tasks when the current work already covers it.
  • Workflow guidance: provide patterns for creating tasks and commenting to track progress across sessions.

Quick Start

Create or update a Trekker task from a bug report or feature discussion.

Frequently Asked Questions about issue-tracking

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

FAQPage Schema
How do I track bugs and features from chat discussions without losing context?▼

Bug and feature tracking from discussions is handled by suggesting Trekker tasks that persist beyond the current session. The workflow surfaces work items from your conversations and prompts you before creating or updating any tracked tasks.

How do I avoid creating duplicate tasks when tracking backlog items?▼

Duplicate tracking is prevented by enforcing duplicate checks before suggesting any task creation. The system searches for existing Trekker entries to avoid fragmentation and updates current tasks when the work already covers the discussion topic.

When do I need to create persistent tasks from a conversation?▼

Persistent task creation is needed when bugs, features, or backlog items should survive beyond the current chat session. If the discussed work requires tracking progress across multiple sessions, the workflow prompts you to create or update a Trekker entry.

Does issue-tracking prompt before updating existing Trekker tasks?▼

Yes, Trekker task updates are safe because the workflow prompts you before creating or updating any tracked items. This ensures you review changes before they are applied to existing backlog entries or bug reports.

What is the best way to manage workflow planning for bugs discussed in chat?▼

Workflow planning for bugs is managed by providing patterns for task creation and commenting to track progress. This approach coordinates Trekker tasks directly from discussions about bugs, features, and backlog items.

Can I update existing tasks instead of creating new ones for the same bug report?▼

Yes, existing tasks are updated when the current work already covers the bug report or feature discussion. The workflow enforces duplicate checks and prompts you to update rather than fragment tracking across multiple entries.

Related Skills

Explore More Software Engineering Skills→
obsfxobsfx

search

Search Trekker tasks, comments, and history using FTS5 queries.

Community
Basic
obsfxobsfx

trekker

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

Community
Intermediate
obsfxobsfx

task-agent

Coordinate Trekker task lifecycles with context recovery and progress updates.

Community
Advanced
microsoftmicrosoft
10

bug

Create GitHub issues from conversational bug reports using the GitHub CLI.

Official
Intermediate