plan-ticket

Generate a copyable YAML ticket contract template with pre-filled fields.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of creating detailed ticket contracts by generating pre-filled YAML templates, eliminating the need to manually structure ticket information.

Core Features & Use Cases

  • Automated Template Generation: Creates a copyable YAML contract for new tickets.
  • Contextual Pre-filling: Populates fields like title, repo, and requirements based on provided context.
  • Use Case: When you need to create a new bug ticket, you can simply run /plan-ticket fix login bug in omnibase_core, and it will output a structured template ready for customization and submission to your ticketing system.

Quick Start

Use the plan-ticket skill to generate a ticket template for adding caching to the API.

Frequently Asked Questions about plan-ticket

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

FAQPage Schema
How do I generate a YAML ticket template for agile planning?

To generate a YAML ticket template, provide context like the ticket title and repository, and the system outputs a copyable contract pre-filled with inferred requirements and verification steps.

What's the best way to create structured ticket contracts without manual formatting?

Creating structured ticket contracts is best handled by automated template generation, which eliminates manual structuring by pre-filling YAML fields based on the planning context you provide.

Can I specify ticket titles and repositories when generating workflow templates?

Yes, you can specify ticket titles and repositories when generating workflow templates, allowing the system to contextually pre-fill the YAML contract with relevant project details.

How does inferring requirements and verification steps work for linear tickets?

Inferring requirements and verification steps works by analyzing the context you provide during ticket creation, automatically populating those fields within the generated YAML contract template.

Does the generated ticket template integrate with other workflow commands?

Yes, the generated ticket template integrates with workflow commands like `/create-ticket` and `/generate-ticket-contract` to complete the end-to-end ticket creation process.