refine

Refine GitHub Issues with acceptance criteria, estimates, and labels.

1|1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/dokipen/claude-cadence --skill refine-dokipen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refine
Source: https://github.com/dokipen/claude-cadence/tree/main/.gemini/skills/refine
Command: npx skills add https://github.com/dokipen/claude-cadence --skill refine-dokipen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refine tickets to meet quality standards before implementation begins.

Core Features & Use Cases

  • Delegate to a ticket-refiner agent to review and enhance issues with acceptance criteria, estimates, priorities, labels, assignments, and blockers.
  • Ensure issues reach a refined state by enforcing workflow transitions and validations across GitHub Issues and the issues microservice.
  • Apply project-specific refinement rules and provide an auditable summary of changes for each ticket.

Quick Start

Refine all open issues by running the refine command in your Claude Cadence environment.

Frequently Asked Questions about refine

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

FAQPage Schema
How do I automate adding acceptance criteria and estimates to GitHub Issues?

Automating acceptance criteria and estimates for GitHub Issues is handled by delegating to a ticket-refiner agent that reviews open issues and enforces quality standards like priority, labels, and assignments before work begins.

Can I batch refine an entire backlog of open tickets at once?

Batch backlog processing is supported, allowing you to refine all open issues simultaneously by running the refine command, which applies project-specific rules, status transitions, and validations across the entire backlog.

How do I enforce assignment and priority rules before development starts?

Assignment enforcement and priority setting are applied during the ticket refinement workflow, validating that each issue has a designated assignee and correct priority label before it transitions to a ready state.

Does the ticket refinement workflow work with both GitHub Issues and custom microservices?

Ticket refinement works with both GitHub Issues and the issues microservice, implementing provider detection to apply the correct workflow transitions, validations, and quality checks across different issue tracking backends.

What's the best way to identify and label blockers in a project backlog?

Identifying and labeling blockers is part of the ticket refinement process, where the agent reviews issues for dependencies, adds blocker labels, and ensures the status reflects blocking conditions before implementation.

How do I get an auditable summary of changes made during ticket refinement?

An auditable summary of changes is provided for each ticket after refinement, documenting all modifications made to acceptance criteria, estimates, assignments, priorities, and labels to ensure full traceability of quality enforcement.