ticket-workflow

Name: ticket-workflow
Availability: InStock
Author: nicolas

Coordinate ticket resolution across fetch, analyze, and planning steps.

Updated Jan 15, 2026

Search Tags:#automation #workflow #planning #integration #resume #ticket #state-machine

Ready to run

npx skills add https://github.com/nicolas-codemate/claudeCodeConfig --skill ticket-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ticket-workflow
Source: https://github.com/nicolas-codemate/claudeCodeConfig/tree/main/skills/ticket-workflow
Command: npx skills add https://github.com/nicolas-codemate/claudeCodeConfig --skill ticket-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Global workflow coordination for ticket resolution with a state machine and resume capability. It coordinates the fetch-ticket, analyze-ticket, plan, and implement phases and integrates with AEP/Architect for planning.

Core Features & Use Cases

End-to-end orchestration of fetch-ticket, analyze-ticket, planning, and implementing phases.
Resume-support to recover from errors and resume from the last validated state.
Integrations with YouTrack and GitHub workflows and collaboration with AEP for exploration and Architect for planning.

Quick Start

Start a ticket workflow with /resolve <ticket-id> to begin the end-to-end process.

Frequently Asked Questions about ticket-workflow

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

FAQPage Schema

How do I automate ticket resolution from fetching to implementation?▼

Ticket resolution automation coordinates fetch-ticket, analyze-ticket, planning, and implementation phases end-to-end. It uses a state machine to orchestrate the workflow, integrating with AEP for exploration and Architect for planning to handle simple to complex tickets.

Can I resume an interrupted ticket workflow after an error?▼

Yes, ticket workflow resume support recovers from errors by restoring the last validated state in the state machine. This allows you to resume the fetch-ticket, analyze-ticket, and planning phases without losing progress on your YouTrack or GitHub tickets.

Does the ticket workflow state machine work with YouTrack and GitHub?▼

Yes, the ticket workflow state machine integrates with both YouTrack and GitHub workflows. It coordinates ticket fetching, analysis, and planning across these platforms, managing structured status graphs and artifacts for end-to-end resolution.

What is the best way to handle complex ticket planning and implementation?▼

The best way to handle complex ticket planning is using a state machine orchestration that integrates with AEP for exploration and Architect for planning. This coordinates the analyze-ticket and planning phases while maintaining structured artifacts for the implementation.

How do I start an end-to-end ticket resolution process?▼

Start the end-to-end ticket resolution process by invoking the resolve command with a ticket identifier. This triggers the state machine to fetch the ticket, analyze it, generate a plan, and proceed through implementation with resume support enabled.

Why does ticket workflow automation need a state machine?▼

Ticket workflow automation needs a state machine to maintain a structured status graph across fetch, analyze, plan, and implement phases. This enables resume support by tracking validated states, coordinating integrations, and recovering from interruptions during complex ticket resolution.