skills.rest
Zate
ZateCOMMUNITY
Explore all skills by this author →
GitHub

issue-tracking

Track bugs, features, tasks, and chores in file-based issue files.

9|2|Updated Dec 5, 2025
Search Tags:#backlog#issues#tracking#devloop#BUG-001
One-click install
npx skills add https://github.com/Zate/cc-plugins --skill issue-tracking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-tracking
Source: https://github.com/Zate/cc-plugins/tree/main/plugins/devloop/skills/issue-tracking
Command: npx skills add https://github.com/Zate/cc-plugins --skill issue-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A unified, file-based issue tracking system that supports multiple item types (bugs, features, tasks, chores, spikes) with type-prefixed IDs and focused views.

Core Features & Use Cases

  • Type-prefixed IDs (BUG-001, FEAT-001) for quick identification.
  • Backlog and views: bugs.md, features.md, backlog.md, and individual issue files.
  • Smart routing: auto-categorization and routing to appropriate views.

Quick Start

Create a new issue file under .devloop/issues/ with a unique prefix and fill in required frontmatter fields.

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 in a file-based system?▼

Issue tracking organizes bugs, features, tasks, and other work items in a file-based system stored under .devloop/issues. Each issue uses type-prefixed IDs like BUG-001 or FEAT-001, required frontmatter fields (id, type, title, status, priority, created, updated, reporter), and auto-generated view files for quick access.

What file structure does a unified issue-tracking system need?▼

A unified issue-tracking system uses .devloop/issues as the root directory with individual issue files containing frontmatter schema fields. The system auto-generates view files—bugs.md, features.md, backlog.md—that categorize and route issues by type for organized backlog management.

Can I manage multiple issue types with type-prefixed IDs?▼

Yes. Type-prefixed IDs like BUG-001, FEAT-001, and TASK-001 support bugs, features, tasks, chores, and spikes in a single system. This naming convention enables quick identification and smart auto-categorization into appropriate view files.

How do I set up required and optional fields for work items?▼

Required frontmatter fields include id, type, title, status, priority, created, updated, and reporter. Optional fields—assignee, labels, related-files, related-plan-task, estimate, due-date—add context when needed. Store all issues as files under .devloop/issues with consistent field structure.

What's the difference between backlog views and individual issue files?▼

Individual issue files store complete work item details with all frontmatter fields. Generated view files—backlog.md, bugs.md, features.md—provide filtered, categorized summaries organized by type, enabling quick scanning without opening each file.

Related Skills

Explore More Software Engineering Skills→
ehtbantonehtbanton

pnpm-workspace-generator

Generate pnpm-workspace.yaml configuration files for pnpm monorepos.

Community
Basic
shogo-labsshogo-labs
12

sprint-board

Create and manage sprint board canvases with kanban columns and velocity tracking.

Official
Advanced
foomakersfoomakers
6

write-issue

Create or update project management issues via API with template-driven formatting.

Official
Advanced
tarekBassiounytarekBassiouny

Najaah LMS - Master Project Skill

Provide comprehensive project context for the Najaah LMS system.

Community
Advanced