ticket-triage

Evaluate development tickets against readiness criteria and provide remediation feedback.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/jwilger/eventcore --skill ticket-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-triage
Source: https://github.com/jwilger/eventcore/tree/main/.agents/skills/ticket-triage
Command: npx skills add https://github.com/jwilger/eventcore --skill ticket-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that development tickets are complete, clear, and actionable, preventing wasted development time and rework due to ambiguous or incomplete requirements.

Core Features & Use Cases

  • Readiness Evaluation: Assesses tickets against six key criteria to determine if they are ready for development.
  • Actionable Feedback: Provides specific, constructive guidance on how to improve tickets that are not ready.
  • Use Case: A product manager pastes a user story into the chat and asks, "Is this ticket ready for the team to start working on?" The skill will analyze the ticket and provide a verdict with detailed feedback.

Quick Start

Use the ticket-triage skill to evaluate the readiness of the following ticket description: "As a user, I want to be able to reset my password so that I can regain access to my account if I forget it."

Frequently Asked Questions about ticket-triage

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

FAQPage Schema
How do I check if a user story is ready for development?

Ticket triage assesses development readiness by evaluating acceptance criteria clarity, scope appropriateness, verifiability, user-centricity, and data model validation. It provides detailed feedback and remediation steps for incomplete or ambiguous user stories before development begins.

What criteria should I use for ticket triage before sprint planning?

Ticket triage criteria include acceptance criteria clarity, scope appropriateness, verifiability, user-centricity, and data model validation. Evaluating these areas ensures user stories are complete, clear, and actionable before sprint planning to prevent wasted development time.

How do I evaluate acceptance criteria for ambiguity in agile requirements?

Evaluating acceptance criteria for ambiguity involves checking verifiability and user-centricity during ticket triage. The process analyzes the ticket against readiness criteria and provides constructive guidance on improving unclear or incomplete requirements.

Can I use requirements analysis to fix incomplete development tickets?

Yes, you can use requirements analysis to fix incomplete development tickets by pasting the user story for triage. It assesses tickets against readiness criteria and provides actionable feedback with specific remediation steps to resolve ambiguity.

Why does scope appropriateness matter during user story review?

Scope appropriateness matters during user story review because it ensures tickets are actionable for development. Triage evaluates scope alongside acceptance criteria clarity to prevent wasted development time and rework caused by improperly sized requirements.