create-tickets

Convert approved Feature Doc Section 5 use cases into engineering tickets for Linear, Jira, or text.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ramybarsoum/RStack-V0 --skill create-tickets-ramybarsoum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-tickets
Source: https://github.com/ramybarsoum/RStack-V0/tree/main/skill/create-tickets
Command: npx skills add https://github.com/ramybarsoum/RStack-V0 --skill create-tickets-ramybarsoum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts approved Feature Docs (PRDs) into clear, testable engineering tickets so product managers and engineers avoid manual ticket writing, missed acceptance criteria, and hidden dependencies.

Core Features & Use Cases

  • Structured ticket generation: Breaks a Feature Doc into component-specific tickets with titles, acceptance criteria sourced from Section 5 use cases, technical notes, and dependencies.
  • Direct or fallback delivery: Creates issues directly in Linear or Jira when MCPs are configured, or generates copy-paste formatted ticket text when they are not available.
  • Planning and estimation: Adds T-shirt sizing or story points, groups work into epics/sprints, and produces a dependency summary and sprint assignment recommendations.
  • Use case: PM runs this immediately after Feature Doc approval to produce a parent epic, child tickets with estimates, and a dependency graph for engineering handoff.

Quick Start

Create tickets from the approved Feature Doc by specifying the source document, target system (Linear, Jira, or text), project/team, ticket type, and priority.

Frequently Asked Questions about create-tickets

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

FAQPage Schema
How do I convert an approved PRD into Jira tickets with acceptance criteria?

The Skill generates engineering tickets from a Feature Doc by breaking it down into component-specific child tickets with titles, acceptance criteria, and dependencies. It extracts use cases from Section 5 of the PRD to ensure testable and clear ticket creation.

Can I create Linear tickets directly from a feature document?

Yes, you can create Linear tickets directly from a feature document when Linear MCPs are configured. The Skill automatically generates a parent epic, child tickets with estimates, and a dependency graph for engineering handoff.

What is the best way to estimate story points and map dependencies from a PRD?

Estimating story points and mapping dependencies from a PRD is handled by grouping the generated tickets into epics or sprints. The Skill adds T-shirt sizing or story points to each ticket and produces a dedicated dependency summary for engineering planning.

How do I generate engineering tickets if I don't have Jira or Linear configured?

To generate engineering tickets without Jira or Linear configured, the Skill produces sequential, copy-paste formatted ticket text as a fallback. This output includes the titles, acceptance criteria, estimates, and a dependency summary for manual ingestion.

Does ticket generation from a Feature Doc support sprint assignment recommendations?

Yes, ticket generation from a Feature Doc supports sprint assignment recommendations. After breaking the document into component-specific tickets with estimates, the Skill groups the work into epics or sprints and outputs suggested sprint assignments.