ticket-refinement

Name: ticket-refinement
Availability: InStock
Author: CivicActions

Refine triaged issue tickets into structured development tasks with acceptance criteria.

2|Updated May 24, 2026

Search Tags:#workflow #refinement #acceptance criteria #technical documentation #jira #ticket

Ready to run

npx skills add https://github.com/CivicActions/ai-runbook-jh --skill ticket-refinement-civicactions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ticket-refinement
Source: https://github.com/CivicActions/ai-runbook-jh/tree/main/skills/ticket-refinement
Command: npx skills add https://github.com/CivicActions/ai-runbook-jh --skill ticket-refinement-civicactions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the ambiguity and lack of detail in raw tickets, ensuring that development work is clearly defined, estimated, and aligned with project standards before implementation begins.

Core Features & Use Cases

Standardized Refinement: Automatically structures ticket bodies with user stories, acceptance criteria, and technical notes based on project-specific contracts.
Context Preservation: Ensures critical links, environment prerequisites, and diagnostic observations are never lost during the refinement process.
Use Case: Use this when a ticket has been triaged but lacks the necessary acceptance criteria or technical context required for a developer to begin work.

Quick Start

Invoke the ticket-refinement skill on the current ticket to generate a complete, tracker-ready ticket body.

Frequently Asked Questions about ticket-refinement

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

FAQPage Schema

How do I refine raw Jira tickets into ready-to-build development tasks?▼

Refining raw Jira tickets involves structuring them with user stories, acceptance criteria, and technical notes. The ticket-refinement skill automates this by applying project-specific contracts to ensure technical dependencies and accessibility requirements are documented before development begins.

What is ticket refinement and when do I need to add acceptance criteria?▼

Ticket refinement is the process of transforming raw triaged issues into actionable tasks. You need to add acceptance criteria when a ticket lacks the necessary technical context or definition-of-done requirements required for a developer to begin implementation.

How do I standardize technical documentation and workflow states across project tickets?▼

To standardize technical documentation and workflow states, you validate ticket content against project-specific contracts. This ensures critical links, environment prerequisites, and diagnostic observations are preserved and aligned with required workflow states before estimation.

Does ticket refinement work on untriaged tickets or do they need preparation first?▼

Ticket refinement operates specifically on triaged tickets, not untriaged ones. Tickets must be initially prepared so the skill can effectively apply project-specific contracts, accessibility requirements, and definition-of-done validations to make them ready for development.

What is the best way to ensure accessibility requirements are documented before ticket estimation?▼

The best way to document accessibility requirements before estimation is to validate ticket content against project-specific definition-of-done requirements. This ensures technical notes, dependencies, and accessibility criteria are explicitly captured during the refinement process.

Why does my development ticket lack the technical context needed to start implementation?▼

Your development ticket lacks technical context because raw tickets often contain ambiguity. Refining them structures the ticket body with user stories, acceptance criteria, and technical notes, ensuring all diagnostic observations and environment prerequisites are documented.