skills.rest
ybaspinar
ybaspinarCOMMUNITY
Explore all skills by this author →
Website𝕏@yusufbaspinarGitHub

structural-triage

Triage tickets, bug reports, and incidents by evidence and blast radius.

Updated May 27, 2026
Search Tags:#ownership#prioritization#issue tracking#triage#incident management#bug reports#severity
One-click install
npx skills add https://github.com/ybaspinar/agent-work-skills --skill structural-triage-ybaspinar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: structural-triage
Source: https://github.com/ybaspinar/agent-work-skills/tree/main/skills/structural-triage
Command: npx skills add https://github.com/ybaspinar/agent-work-skills --skill structural-triage-ybaspinar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Incoming tickets, bug reports, and incidents often arrive with asserted priorities, incomplete evidence, and loud reporters, making it hard to decide what is real, how urgent it is, and who owns it next. ## Core Features & Use Cases - Evidence-Based Ranking: Re-derives the real problem from logs, traces, repro steps, and affected scope instead of trusting reporter claims. - Blast-Radius Severity Sizing: Ranks issues by corruption risk, security exposure, attacker-controlled paths, and customer impact rather than thread volume. - Explicit Disposition and Ownership: Forces every triaged issue to end with one owner, a revealing title, and a fix-now, schedule, spike, or won't-fix decision. - Use Case: A screenshot-based bug report claims data loss. Use this Skill to attempt reproduction, size the actual blast radius, assign an owner, and file the missing observability signal as a separate issue. ## Quick Start Triage this incoming bug report and give me the evidence summary, severity assessment, owner, and disposition.

Frequently Asked Questions about structural-triage

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

FAQPage Schema
How do I triage bug reports with incomplete information?▼

Treat the report as untrusted input and re-derive the problem from logs, traces, and repro steps. If it is not reproducible, mark it unconfirmed unless the potential blast radius justifies a bounded spike to find a repro.

How to prioritize incidents by severity and impact?▼

Rank by blast radius: data corruption, security exposure, attacker-controlled paths, and wide customer impact outrank loud but contained pain. Use shipped signals to size severity, and file observability gaps as separate issues.

What should a triage decision include?▼

Every triaged issue needs one owner of record, a title naming the failure mode, and an explicit disposition: fix-now, schedule, needs-a-spike, or won't-fix. No issue should remain open without an owner, disposition, and reason.

When should triage not attempt to fix the bug?▼

Triage decides whether and how urgently an issue moves, not the design of the fix. Debugging the whole solution inside triage is a red flag; hand the how to the next phase with a clear handoff artefact.

Is a screenshot enough evidence to confirm a bug?▼

No. A screenshot is not a reproduction. Confirm the issue through logs, traces, data, or reproducible steps before ranking it, or mark it unconfirmed pending a bounded investigation.

Related Skills

Explore More Software Engineering Skills→
cursorcursor
6.6k

triage-issue-reports

Classifies Slack issue reports and posts one verdict with tracker dedupe and routing.

Official
Advanced
ahsanghalibahsanghalib

brainstorming

Refine vague ideas into user-approved designs through structured collaborative questioning.

Community
Intermediate
CaneproCanepro

observability-architecture

Design observability architecture for metrics, logs, traces, dashboards, and alert routing.

Community
Advanced
vndeevndee
3

incident-response

Coordinate structured incident response workflows for production outages.

Community
Advanced