ticket

Convert ambiguous user descriptions into structured PM tickets with defined fields.

24|5|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/yves-s/just-ship --skill ticket-yves-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket
Source: https://github.com/yves-s/just-ship/tree/main/skills/ticket
Command: npx skills add https://github.com/yves-s/just-ship --skill ticket-yves-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps teams convert vague user descriptions into a well-defined product-management ticket with clear structure and scope, enabling faster triage and planning.

Core Features & Use Cases

  • Structured ticket generation: produces a PM-quality ticket with Title, Problem, Desired Behavior, Acceptance Criteria, and Out of Scope.
  • Split and grouping support: can trigger Epic creation with child tickets or group existing tickets under a new Epic.
  • No-code, deterministic workflow: outputs the ticket without performing any code changes or deployments.
  • Use Case: a product manager or engineer submits a feature idea and the skill delivers a ready-to-run ticket for the planning board.

Quick Start

Provide a concise user input describing the ticket, and the skill will produce a PM-quality ticket.

Frequently Asked Questions about ticket

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

FAQPage Schema
How do I convert vague user input into a structured product management ticket?▼

To convert vague user input into a structured product management ticket, provide the raw feature description to this Skill. It outputs a formatted PM ticket containing a title, problem statement, desired behavior, acceptance criteria, and out-of-scope sections.

Can I split a large feature request into an Epic with child tickets?▼

Yes, you can split a large feature request into an Epic with child tickets. The Skill supports Epic splitting workflows, automatically generating child tickets or grouping existing tickets under a newly created Epic for structured backlog management.

What fields are included in a generated PM backlog ticket?▼

A generated PM backlog ticket includes specific fields: Title, Problem, Desired Behavior, Acceptance Criteria, and Out of Scope. This structure ensures clear scope definition and enables faster triage for product planning workflows.

Do I need the just-ship-ticket-writer workflow to generate tickets?▼

Yes, you need the just-ship-ticket-writer workflow to generate tickets. The Skill requires integration with this specific workflow to properly convert ambiguous user descriptions into a deterministic, PM-quality output without modifying code.

Can this ticket creation Skill write code or deploy changes to my project?▼

No, this ticket creation Skill cannot write code or deploy changes to your project. It is a no-code, deterministic workflow that strictly outputs structured planning tickets and performs no modifications to your codebase or deployment environment.