issue-management-guidelines

Standardize issue creation, labeling, and lifecycle management with templates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RevTechStudio/rts-plugins --skill issue-management-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-management-guidelines
Source: https://github.com/RevTechStudio/rts-plugins/tree/main/rts-foundation/skills/issue-management-guidelines
Command: npx skills add https://github.com/RevTechStudio/rts-plugins --skill issue-management-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes templates (resource) components.

What problem does it solve?

This Skill standardizes the creation, classification, and management of project issues, bugs, and tasks. It ensures clarity, efficient prioritization, and effective progress tracking, reducing miscommunication and improving project visibility.

Core Features & Use Cases

  • Structured Issue Creation: Provides guidelines for writing concise titles, detailed descriptions (including reproduction steps for bugs), and clear completion criteria.
  • Template-Based Reporting: Defines and utilizes templates for bug reports, feature requests, and general tasks, ensuring all necessary information is captured.
  • Labeling & Lifecycle Management: Establishes rules for applying type, priority, and status labels, and guides issues through their lifecycle from creation to closure.
  • Use Case: A team member discovers a bug. They use this skill to create a bug report following a template, including reproduction steps, expected vs. actual behavior, and environment details, then assign appropriate labels and link it to a pull request for resolution.

Quick Start

Explain the guidelines for creating a new bug report, including title format, required sections, and how to use labels.

Frequently Asked Questions about issue-management-guidelines

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

FAQPage Schema
How do I create consistent bug reports with all necessary information?

Structured bug reporting captures reproduction steps, expected vs. actual behavior, and environment details using a template format. This ensures team members can quickly understand and prioritize issues without back-and-forth clarification.

What's the best way to organize and track issues across a software project?

Apply type, priority, and status labels to issues and guide them through a defined lifecycle from creation to closure. Labeling rules and lifecycle workflows enable efficient prioritization and visibility into project progress.

How should I title and describe issues to make them actionable?

Use concise, descriptive titles and include context such as background information and clear completion criteria in the description. This structure reduces miscommunication and helps team members quickly assess scope and requirements.

Can I use issue templates to standardize bug reports and feature requests?

Yes. Template-based reporting for bugs, feature requests, and tasks ensures all necessary information is consistently captured, reducing incomplete submissions and improving issue quality across your project.

Why link issues to pull requests in my workflow?

Explicit cross-referencing between issues and pull requests creates traceability and clarifies the relationship between reported problems and their resolutions, improving project tracking and team communication.

What labeling rules should I apply to manage issue types and priorities?

Establish consistent rules for type labels (bug, feature, task), priority levels, and status indicators. These categories enable quick filtering, prioritization, and progress tracking across your issue backlog.