create-ticket

Generate local JSON tickets from spec files with YAML frontmatter.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of local JSON tickets from spec files, streamlining project management and saving time in ticketing processes.

Core Features & Use Cases

  • Ticket Creation from Spec Files: Reads Phase 1 features from spec files and generates corresponding local JSON tickets.
  • Offline Operation: Operates without GitHub dependencies, ensuring offline functionality.
  • Use Case: Ideal for projects using H-Consensus models where tickets are generated based on sprint contracts.

Quick Start

To create tickets from the latest spec file, use: /create-ticket

Frequently Asked Questions about create-ticket

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

FAQPage Schema
How do I generate local JSON tickets from spec files for project management?

To generate local JSON tickets, you execute a script that reads Phase 1 features from spec files and outputs corresponding local JSON tickets. This process uses YAML frontmatter for configuration and Markdown for instructions.

Can I create project tickets offline without relying on GitHub?

Yes, you can create project tickets offline without relying on GitHub. This ticket generation process operates entirely locally, reading spec files to produce JSON tickets for issue tracking without external platform dependencies.

How does generating tickets from spec files work for sprint planning?

Generating tickets from spec files works by reading Phase 1 features defined in the spec and creating local JSON tickets. This approach is ideal for projects using H-Consensus models where tickets map directly to sprint contracts.

Do I need script execution to create local JSON tickets from spec files?

Yes, script execution is required to create local JSON tickets from spec files. The Skill relies on scripts to parse the YAML frontmatter and Markdown instructions within the spec file to automate the ticketing process.

What is the best way to track issues locally using spec files?

The best way to track issues locally is to generate JSON tickets directly from your spec files. This streamlines issue tracking by converting phase features into structured local data without relying on external project management platforms.

Are there limitations when using local JSON tickets for project management?

A limitation of using local JSON tickets is that they operate offline without GitHub integration, meaning ticket synchronization across remote teams is absent. It is best suited for local project management and isolated sprint planning workflows.