ticket-work

Orchestrate contract-driven ticket execution through Linear-integrated lifecycle phases.

3|1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill ticket-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-work
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/ticket-work
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill ticket-work

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the end-to-end execution of software development tickets, ensuring adherence to defined phases and integrating seamlessly with Linear for status tracking.

Core Features & Use Cases

  • Contract-Driven Workflow: Manages ticket execution based on a YAML contract defined within the ticket description, covering phases from intake to done.
  • Automated Phase Transitions: Orchestrates transitions between intake, research, questions, specification, implementation, review, and done, with configurable human gates.
  • Integration with Linear: Updates ticket status, creates branches, and manages PRs directly within Linear.
  • Use Case: Automatically move a ticket from 'To Do' to 'In Progress', create a feature branch, guide you through implementation, run verification tests, and prepare a pull request for review, all managed by the skill.

Quick Start

Use the ticket-work skill to start working on ticket OMN-1234.

Frequently Asked Questions about ticket-work

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

FAQPage Schema
How do I automate Linear ticket workflows with Git branch creation?

Automate Linear ticket workflows by orchestrating contract-driven execution phases from intake to completion. The skill automatically updates Linear ticket statuses, creates Git feature branches, and manages pull requests using a defined YAML contract. It requires Linear API access and Git CLI to function.

What is contract-driven ticket execution in software development?

Contract-driven ticket execution manages software development phases using a YAML contract defined within the Linear ticket description. It enforces structured transitions through intake, research, specification, implementation, review, and completion phases with configurable human gates for controlled progression.

Can I enforce human approval gates during automated ticket lifecycle transitions?

Yes, you can enforce human gates during automated ticket lifecycle transitions. The contract-driven workflow supports configurable human approval gates between phases like research, specification, implementation, and review, ensuring manual oversight before proceeding to the next stage.

Does this ticket automation tool require Linear API access and Git CLI?

Yes, full functionality requires both Linear API access and Git CLI. Linear API access enables ticket status updates and tracking, while Git CLI handles automated branch creation and pull request management to orchestrate the complete ticket lifecycle end-to-end.

How do I automatically move a Linear ticket from To Do to In Progress?

Automatically move a Linear ticket from To Do to In Progress by initiating the ticket-work skill with your ticket identifier. The skill orchestrates phase transitions, creates feature branches, guides implementation, runs verification, and prepares pull requests for review.

What are the limitations of automating Linear ticket execution with Git operations?

Limitations include requiring both Linear API access and Git CLI for full functionality. The contract-driven workflow depends on a YAML contract within the ticket description, and automated phase transitions are constrained by configurable human gates that pause execution for manual approval.