Unified Issue Tracking FAQs

Question 1

What happens when I update an issue's status?

Accepted Answer

The skill follows strict view generation rules. Whenever an issue is updated, it automatically regenerates the master index, the type-specific views, and the backlog to ensure your project overview is always accurate.

Question 2

Does this require an external database or SaaS subscription?

Accepted Answer

No, this is a local-first system. All issues are stored as standard Markdown files within your repository, allowing them to be versioned with Git and edited with any text editor.

Question 3

Can I use this for non-bug tasks?

Accepted Answer

Yes, the system is designed for unified tracking. It includes specific types and workflows for features, technical tasks, chores (maintenance), and spikes (research/POC).

Question 4

How are issue IDs generated in this skill?

Accepted Answer

IDs are type-prefixed (e.g., BUG-001, FEAT-042) and use an automated counter that scans existing Markdown files in the .devloop/issues/ directory to find the next available number.

Question 5

Does it support priority levels?

Accepted Answer

Yes, issues can be assigned priority levels from Low to Critical. The master index view automatically groups open issues by priority to help you focus on the most important work.

Unified Issue Tracking

Key Features

Use Cases

Unified Issue Tracking

Key Features

Use Cases