skills.rest
Julian0444
Julian0444COMMUNITY
Explore all skills by this author →
𝕏@Julian_Irusta04GitHub

onex-plan-ticket

Convert plan descriptions into YAML tickets and create them in Linear.

2|2|Updated Mar 28, 2026
Search Tags:#yaml#linear integration#ticket creation#repository detection#plan to ticket
One-click install
npx skills add https://github.com/Julian0444/omnicursor --skill onex-plan-ticket
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: onex-plan-ticket
Source: https://github.com/Julian0444/omnicursor/tree/main/.cursor/skills/onex-plan-ticket
Command: npx skills add https://github.com/Julian0444/omnicursor --skill onex-plan-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of converting a plan or task description into a structured ticket, reducing manual effort and ensuring accurate ticket creation.

Core Features & Use Cases

  • Repo Detection: Automatically identifies the appropriate repository for the ticket.
  • YAML Ticket Template: Generates a YAML template with pre-filled information for easy ticket creation.
  • Integration with Linear: Creates tickets directly in Linear using the OmniNode stack.

Quick Start

Generate a ticket for your plan using the 'onex-plan-ticket' skill.

Frequently Asked Questions about onex-plan-ticket

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

FAQPage Schema
How do I automate Linear ticket creation from a plan description?▼

Automate Linear ticket creation by converting a plan description into a structured YAML ticket template with deterministic repository detection. The Skill integrates directly with Linear via the OmniNode stack to pre-fill and generate tickets automatically.

How does repository detection work when generating YAML tickets from plans?▼

Repository detection for YAML ticket generation works by analyzing the repository README.md to automatically identify the appropriate target repository. It uses the OmniNode stack to deterministically map plan descriptions to the correct codebase.

Do I need a README.md file to use deterministic repo detection for ticket creation?▼

Yes, repository detection requires access to the target repository's README.md file. The Skill uses this README.md context to accurately determine the correct repository before generating the YAML ticket template.

Can I pre-fill a YAML ticket template before creating a Linear issue?▼

Yes, you can pre-fill a YAML ticket template before creating a Linear issue. The Skill converts your plan description into a structured YAML format, automatically populating the template fields for seamless Linear ticket creation.

What is the best way to convert task descriptions into structured Linear tickets?▼

The best way to convert task descriptions into structured Linear tickets is using a Skill that combines deterministic repo detection with YAML template generation. This approach reduces manual effort by mapping plan context directly to the correct repository.

Does the plan to ticket conversion process require the OmniNode stack?▼

Yes, the plan to ticket conversion process requires the OmniNode stack for both deterministic repository detection and linear ticket creation. The stack provides the necessary infrastructure to bridge plan descriptions with the Linear API.

Related Skills

Explore More Product & Management Skills→
frankxaifrankxai
6

orchestration/gencreator-stack

Audit AI stacks across repos and emit constellation files, scaffolds, drift reports from inventory.json and STACK.md files.

Community
Advanced
GainInsightDevGainInsightDev

af-linear-issues

Create, update, and query Linear issues via the Linear API.

Official
Intermediate
fmoda3fmoda3
42

doc-sync

Sync CLAUDE.md and README.md files across a repository.

Community
Basic
bostonaholicbostonaholic
8

tracking-tickets

Synchronize pull request statuses with external issue trackers and manage ticket transitions.

Community
Advanced