learn-se-issue

Create a complete issue lifecycle exercise for tracking bugs from discovery to closure.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/novel-jp/projsight-plugin --skill learn-se-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn-se-issue
Source: https://github.com/novel-jp/projsight-plugin/tree/main/skills/learn-se-issue
Command: npx skills add https://github.com/novel-jp/projsight-plugin --skill learn-se-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill teaches how to manage a bug report from discovery through task creation, fix, and closure while preserving traceability.

Core Features & Use Cases

  • Issue lifecycle practice from open to resolved or closed.
  • Severity selection for bugs based on impact and user reach.
  • Task-to-issue linking so the fix history stays auditable.
  • Use case: practice a realistic defect scenario, create the issue, assign a fix task, complete the work, and close the issue.

Quick Start

Use this skill to turn a reported bug into a linked task, complete the fix, and resolve the issue with full traceability.

Frequently Asked Questions about learn-se-issue

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

FAQPage Schema
How do I track a bug from report to resolution with full traceability?

Bug tracking with traceability requires creating an issue, linking it to a fix task, executing the task, and updating issue status upon completion to ensure closed-loop tracking from discovery to closure.

What is the issue lifecycle workflow for managing defects?

The issue lifecycle workflow for defect management involves issue creation, severity selection, task creation, task-issue linking, work start and completion steps, and status updates for auditable closed-loop tracking.

How do I link a task to an issue for auditable bug management?

Task-to-issue linking connects the fix task directly to the reported defect, ensuring the work history stays auditable and the bug management process maintains traceability from task creation through resolution.

How do I assign severity to a bug based on impact and user reach?

Severity selection for bugs involves evaluating the defect's impact and user reach to determine its priority level, ensuring appropriate classification during the issue creation phase of the tracking workflow.

Can I practice issue tracking scenarios for specification-engineering training?

Yes, issue tracking practice is designed for specification-engineering training scenarios where an AI must turn a reported defect into a linked task, execute a fix, and resolve the issue with full traceability.

What are the limitations of closed-loop issue tracking for bug management?

Closed-loop issue tracking requires completing every step from issue creation through status updates; skipping task-issue linking or work completion steps breaks the traceability chain needed for auditable bug management.