ticket-cycle

Automate branch creation, implementation, and verification from local JSON tickets.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/4armsxlr8/ccx-arsenal --skill ticket-cycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-cycle
Source: https://github.com/4armsxlr8/ccx-arsenal/tree/main/plugins/agent-core/skills/ticket-cycle
Command: npx skills add https://github.com/4armsxlr8/ccx-arsenal --skill ticket-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the execution of actions based on local JSON tickets, streamlining the workflow for tasks that don't fit TDD, such as deletions, refactoring, infrastructure changes, configuration updates, and documentation updates.

Core Features & Use Cases

  • Ticket-driven Execution: Automates the creation of branches, implementation, and verification of tasks specified in local JSON tickets.
  • No GitHub Dependency: Fully offline operation, no reliance on GitHub or GitHub API.
  • Use Case: For example, when you need to refactor a part of your codebase that doesn't require TDD, you can use this Skill to automatically create a branch, implement the changes, and verify them without leaving your local environment.

Quick Start

To start the ticket cycle for a ticket with ID 'T-0003', use the command: /ticket-cycle T-0003

Frequently Asked Questions about ticket-cycle

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

FAQPage Schema
How do I automate local JSON ticket execution for refactoring tasks without using GitHub?

Automating local JSON ticket execution for refactoring tasks is handled by creating branches, implementing changes, and verifying actions offline without relying on the GitHub API. The process reads local JSON tickets to drive the entire workflow within your local environment.

Can I execute infrastructure changes and configuration updates without TDD?

Yes, you can execute infrastructure changes and configuration updates without TDD. The ticket-driven workflow is specifically designed for non-TDD tasks like deletions, refactoring, and documentation updates, automating the implementation from local JSON tickets.

What is AC-driven development for offline ticket execution?

AC-driven development for offline ticket execution is a workflow where Acceptance Criteria specified in local JSON tickets dictate the automated creation of branches, implementation, and verification of code changes entirely within your local environment.

Do I need Python to run an offline ticket management workflow?

Yes, Python is required to run this offline ticket management workflow. Along with Python, various command-line tools are necessary to execute the automated branch creation, implementation, and verification steps locally.

How do I start a ticket cycle for a specific task ID?

To start a ticket cycle for a specific task ID, you use the command `/ticket-cycle` followed by your ticket ID, such as `/ticket-cycle T-0003`. This initiates the automated execution of actions defined in the corresponding local JSON ticket.