skills.rest
mpazaryna
mpazarynaCOMMUNITY
Explore all skills by this author →
GitHub

ticket

Create ClickUp tickets from PRDs with acceptance criteria and traceability links.

1|Updated Sep 17, 2025
Search Tags:#task management#workflow automation#specification#prd#clickup#ticket creation
One-click install
npx skills add https://github.com/mpazaryna/agentic-factory --skill ticket-mpazaryna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket
Source: https://github.com/mpazaryna/agentic-factory/tree/main/pm/orchestra/skills/ticket
Command: npx skills add https://github.com/mpazaryna/agentic-factory --skill ticket-mpazaryna

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of converting product requirements documents (PRDs) or specifications into actionable tickets within a task tracking system like ClickUp, ensuring work items are properly defined and prioritized.

Core Features & Use Cases

  • Ticket Creation: Automatically generates a new ticket in ClickUp based on PRD and spec details.
  • Structured Data Extraction: Parses PRDs and specs to extract title, objective, success criteria, and approach.
  • Priority Determination: Helps in assigning an appropriate priority level (Urgent, High, Normal, Low) based on PRD context.
  • Traceability: Links tickets back to their source PRD, spec, and milestone for clear lineage.
  • Use Case: After writing a PRD for a new feature, use this Skill to create a ClickUp ticket, ensuring the development team has a clear objective and acceptance criteria before starting work.

Quick Start

Use the ticket skill to create a ClickUp ticket for the work item located at .orchestra/work/new-feature/.

Frequently Asked Questions about ticket

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

FAQPage Schema
How do I create ClickUp tickets from a PRD?▼

The ticket creation process extracts the title, objective, success criteria, and approach from your PRD. It then generates a structured ClickUp ticket and links it back to the source PRD, spec, and milestone for clear lineage.

How do I set ticket priority based on a product specification?▼

By analyzing PRD context, the system assigns a priority level of Urgent, High, Normal, or Low to the ClickUp ticket. This ensures work items are properly prioritized before the development team starts work.

What do I need to automate ClickUp ticket creation from markdown files?▼

You need a ClickUp API key, a list ID, and a work item folder containing at least a prd.md file. These inputs provide the authentication and source content required to generate a trackable task with objective and acceptance criteria.

How does traceability work when converting PRDs into trackable tasks?▼

Traceability is established by linking the generated ClickUp ticket back to its source PRD, spec, and milestone. This provides clear lineage so the development team can trace objectives and acceptance criteria to their origin.

Can I use this workflow automation for product requirements documents outside of ClickUp?▼

No, this workflow automation requires a ClickUp API key and list ID to function. It is specifically designed to parse product requirements documents and generate trackable tasks within the ClickUp project management system.

Related Skills

Explore More Product & Management Skills→
dpaola2dpaola2
3

prd

Generate a structured Product Requirement Document from a work item brief.

Community
Advanced
NIMBUS-MXNIMBUS-MX

sprint-planning

Automate sprint planning in ClickUp by assigning tickets based on team capacity and prioritization criteria.

Official
Advanced
topastro73-ittopastro73-it
9

ClickUp Skill

Create and update ClickUp Epics and Tasks from product specs via MCP.

Community
Advanced
SamyakJhaveriSamyakJhaveri

to-issues

Convert plans, specs, or PRDs into tracker issues with vertical slices.

Community
Advanced