Ticket Generation Skill

Generate implementation tickets with acceptance criteria and dependency mapping from design documents.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/jackmoch/lasso --skill ticket-generation-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Ticket Generation Skill
Source: https://github.com/jackmoch/lasso/tree/main/.claude/skills/ticket-generation
Command: npx skills add https://github.com/jackmoch/lasso --skill ticket-generation-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of breaking down large features or epics into smaller, manageable, and actionable development tasks, ensuring a clear and efficient workflow.

Core Features & Use Cases

  • Structured Task Creation: Generates tickets with predefined fields like Type, Priority, Effort, Dependencies, Description, Acceptance Criteria, and Implementation Details.
  • Decomposition Guidance: Provides rules for breaking down Epics into User Stories and User Stories into Tasks, with clear guidelines on task sizing.
  • Dependency Mapping: Helps visualize and define task dependencies for better sprint planning.
  • Use Case: When presented with a Product Requirements Document (PRD) for a new feature, this Skill can generate a detailed list of implementation tasks, complete with acceptance criteria and estimated effort, ready for a sprint backlog.

Quick Start

Generate implementation tickets for Sprint 3 (Authentication backend) based on PRD Epic 1 and TDD Section 5.1.

Frequently Asked Questions about Ticket Generation Skill

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

FAQPage Schema
How do I break down a PRD into actionable development tickets?

Breaking down a PRD into actionable development tickets involves decomposing epics and user stories into granular tasks. This Skill automates that by generating tickets with descriptions, acceptance criteria, effort estimates, and dependency mapping from your design documents.

What is the best way to decompose agile epics into sprint planning tasks?

The best way to decompose agile epics for sprint planning is to use decomposition rules that size tasks appropriately. This Skill structures units with type, priority, dependencies, and implementation details to facilitate efficient backlog management.

Can I generate task dependencies and effort estimates from a technical design document?

Generating task dependencies and effort estimates from a technical design document is supported. The Skill outputs structured tickets that visualize task dependencies and provide effort estimates alongside descriptions and acceptance criteria.

Does this task generation approach work for backlog management without external integrations?

This task generation approach works for backlog management without external dependencies. It autonomously structures tasks, maps dependencies, and generates acceptance criteria directly from input documents, requiring no external integrations.

How do I structure acceptance criteria when creating implementation tickets?

Structuring acceptance criteria when creating implementation tickets involves defining clear validation conditions. This Skill automatically generates tickets with structured acceptance criteria, implementation details, and dependency mapping based on your technical design documents.