write-tickets

Convert unstructured inputs into structured Jira ticket markdown via a three-step pipeline.

Updated Feb 23, 2019
One-click install
npx skills add https://github.com/JohnWebb4/dotfiles --skill write-tickets-johnwebb4
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-tickets
Source: https://github.com/JohnWebb4/dotfiles/tree/main/.cursor/skills/write-tickets
Command: npx skills add https://github.com/JohnWebb4/dotfiles --skill write-tickets-johnwebb4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Convert unstructured inputs (meetings notes, Slack threads, rough ideas) into well-structured Jira tickets. This skill orchestrates a three-step pipeline (Research → Write) to produce ready-to-publish ticket markdown using a consistent templated format.

Core Features & Use Cases

  • Three-step pipeline (Research → Write) with subagents, passing data via temp files.
  • Generates ticket markdown using templates (feature, bug, tech debt, spike) and a manifest for publish.
  • Provides clear handoff via /tmp files for review before Jira creation.
  • Supports requirements from notes, conversations, or other inputs and outputs a reusable ticket doc.
  • Allows cross-ticket references and dependency ordering.

Quick Start

Provide your requirements and any supporting context, then run the three-step pipeline starting with Step 1: Research.

Frequently Asked Questions about write-tickets

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

FAQPage Schema
How do I convert meeting notes into structured Jira tickets?▼

To convert meeting notes into Jira tickets, you can use a three-step pipeline that processes unstructured inputs and generates ready-to-publish ticket markdown using consistent templates for features, bugs, or tech debt.

What is the best way to automate Jira ticket creation from Slack threads?▼

Automating Jira ticket creation from Slack threads involves identifying the unstructured requirements and passing them through a research and writing pipeline to output a reusable ticket document formatted for Jira.

Can I generate markdown for different Jira issue types like bugs and spikes?▼

Yes, you can generate markdown for different Jira issue types including bugs, features, tech debt, and spikes by applying template-based ticket generation to structure your rough notes consistently.

How does the ticket generation pipeline handle data between steps?▼

The ticket generation pipeline handles data between steps by using temp files to pass information, providing a clear handoff for review via the /tmp directory before final Jira ticket creation.

Does the Jira ticket writing workflow support cross-ticket references and dependencies?▼

Yes, the Jira ticket writing workflow supports cross-ticket references and dependency ordering, allowing you to manage complex project management tasks and operations directly from your generated markdown manifest.