tpo-bug-tracking-template

Structures bug reports with severity classification, reproduction steps, and fix acceptance criteria.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-bug-tracking-template-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tpo-bug-tracking-template
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/tpo-bug-tracking-template
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-bug-tracking-template-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug reports often arrive incomplete, missing reproduction steps, evidence, or severity classification, which slows triage and causes miscommunication between product owners and developers. This Skill provides a complete bug tracking template that standardizes how bugs are captured, classified, assigned, verified, and closed. ## Core Features & Use Cases - Structured Bug Reports: Capture metadata, expected vs. actual behavior, reproduction steps, and evidence in a consistent format. - Severity and Priority Classification: Classify bugs with S0-S4 severity and P0-P4 priority scales, plus release blocker and security flags. - Fix Assignment and Acceptance: Hand off bugs to an AI Developer Agent with a structured fix task format and verify fixes against acceptance criteria. - Use Case: A Technical Product Owner receives a user complaint about a broken login flow, fills in the template with reproduction steps and screenshots, assigns it S1/P1, and hands a structured fix task to the developer agent with clear acceptance criteria. ## Quick Start Use the bug tracking template to document and triage this reported issue, then generate a fix task for the developer agent.

Frequently Asked Questions about tpo-bug-tracking-template

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

FAQPage Schema
How do I write a good bug report for a developer?

A good bug report includes a clear title, expected versus actual behavior, numbered reproduction steps, environment details, and attached evidence such as screenshots or logs. This template structures all of these fields so another person or AI agent can reproduce the issue without guessing.

How to classify bug severity and priority?

Severity measures technical impact from S0 (system down, data loss) to S4 (cosmetic), while priority measures fix urgency from P0 (immediately) to P4 (backlog). The template also flags release blockers, security sensitivity, and customer impact level.

What should a bug fix acceptance criteria checklist include?

Acceptance criteria should confirm the original bug no longer reproduces, the fix stays within scope, tests are added or updated, existing tests pass, and regression risk is reviewed. The template also requires verification in the correct environment before closure.

Can I use this bug template with Jira or GitHub Issues?

Yes, the template includes a dashboard fields section mapping each field to common issue tracker types like select, date, and person fields. You can replicate the structure in Jira, GitHub Issues, spreadsheets, or project boards.

When should a bug be closed as won't fix or deferred?

Close as won't fix when the cost or risk of fixing outweighs the impact, and as deferred when the fix is valid but not scheduled. The closure notes section records the resolution reason, follow-up tasks, and lessons learned for traceability.