skills.rest
dokipen
dokipenCOMMUNITY
Explore all skills by this author →
GitHub

ticket-refiner

Refine GitHub Issues and issues-api tickets with Cadence criteria.

1|1|Updated Mar 5, 2026
Search Tags:#workflow#github#quality#ticket#refine#issues-api
One-click install
npx skills add https://github.com/dokipen/claude-cadence --skill ticket-refiner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-refiner
Source: https://github.com/dokipen/claude-cadence/tree/main/codex/skills/ticket-refiner
Command: npx skills add https://github.com/dokipen/claude-cadence --skill ticket-refiner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and refine tickets for quality and completeness to streamline issue triage and resolution.

Core Features & Use Cases

  • Specialist-role wrapper aligns ticket content with Cadence review criteria across GitHub Issues and issues-api backends.
  • Provides standardized guidance for refining tickets, including acceptance criteria clarity, scope, and traceability.
  • Use Case: during a ticket refinement session, feed in a ticket and receive structured suggestions to improve description, requirements, and links to the source of truth.

Quick Start

To begin, provide a ticket to be refined and instruct the model to apply the Cadence ticket refinement criteria from the source files.

Frequently Asked Questions about ticket-refiner

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

FAQPage Schema
How do I refine GitHub issues for quality and completeness during triage?▼

To refine GitHub issues, you feed the ticket into the refiner to enforce Cadence rules, clarify acceptance criteria, and generate an improved description with traceability to the source of truth.

What is ticket refinement and how does it improve issue triage?▼

Ticket refinement is the process of reviewing issues to ensure quality and completeness. It improves triage by standardizing descriptions, clarifying acceptance criteria, and enforcing source-of-truth usage for better resolution outcomes.

Can I use this ticket refiner with the issues-api backend?▼

Yes, you can use this ticket refiner with the issues-api backend. It is specifically designed to align ticket content with Cadence review criteria across both GitHub Issues and issues-api backends.

How do I apply Cadence rules to improve ticket acceptance criteria and scope?▼

You apply Cadence rules by providing a ticket and instructing the model to use the Cadence refinement criteria from the source files, which generates structured suggestions for scope, requirements, and acceptance criteria.

What's the best way to enforce source-of-truth usage when reviewing GitHub tickets?▼

The best way to enforce source-of-truth usage is to run tickets through a refinement process that checks Cadence rules adherence and outputs structured suggestions linking requirements back to the original source of truth.

Why does ticket refinement focus on traceability and acceptance criteria?▼

Ticket refinement focuses on traceability and acceptance criteria because clear requirements and source-of-truth links streamline issue triage and ensure development teams resolve the correct scope without ambiguity.

Related Skills

Explore More Software Engineering Skills→
cdubiel08cdubiel08
2

form

Transform unstructured ideas into structured GitHub issues or ticket trees.

Community
Advanced
saolalabsaolalab
37

ticket-management

Create and manage support tickets through triage, assignment, and SLA tracking.

Official
Intermediate
openshift-engopenshift-eng
7

two-node:create-rhel-stories

Create OCPEDGE backlog stories from grouped RHEL TNF verification tickets via Jira.

Official
Advanced
githubnextgithubnext
4

apm-triage-panel

Orchestrate a specialist panel to review and decide issue status.

Official
Advanced