work-tracker

Track bugs, tasks, ideas, and decisions in markdown files.

25|5|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/Nimbalyst/skills --skill work-tracker-nimbalyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-tracker
Source: https://github.com/Nimbalyst/skills/tree/main/skills/product/work-tracker
Command: npx skills add https://github.com/Nimbalyst/skills --skill work-tracker-nimbalyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of logging and tracking various work-related items such as bugs, tasks, ideas, and decisions, ensuring nothing gets lost and progress is maintained.

Core Features & Use Cases

  • Categorized Tracking: Organizes items into predefined types like bugs, tasks, ideas, decisions, feature requests, user stories, feedback, and tech debt.
  • Automated Item Creation: Generates unique IDs and assigns priorities based on keywords.
  • Use Case: A developer can quickly log a bug encountered during testing using a simple command, ensuring it's captured and prioritized for resolution.

Quick Start

Use the /track command to log a new bug with the description "Login fails on mobile Safari".

Frequently Asked Questions about work-tracker

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

FAQPage Schema
How do I track bugs and tasks in markdown files?

To track bugs and tasks in markdown files, use the /track command to automatically generate unique IDs, detect item types, and assign priorities based on descriptive keywords.

What is the best way to log work items and decisions for a local project?

Logging work items and decisions locally is best handled by categorizing entries into bugs, tasks, ideas, or feature requests within markdown files to ensure nothing gets lost.

Can I automatically assign priorities to feature requests and tech debt?

Yes, you can automatically assign priorities to feature requests and tech debt by using specific descriptive keywords when logging the item.

Does work item tracking support dynamic type detection for ideas and user stories?

Work item tracking supports dynamic type detection for ideas and user stories by analyzing descriptive keywords in the input to categorize the logged item accurately.

How do I log a bug encountered during testing without interrupting my workflow?

You can log a bug without interrupting your workflow by using a simple /track command with the bug description, which captures and prioritizes the item instantly.