receiving-tickets

Fetch Jira ticket data and create a standardized project workspace with documentation.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/dogkeeper886/ai-qa-workflow --skill receiving-tickets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-tickets
Source: https://github.com/dogkeeper886/ai-qa-workflow/tree/main/skills/receiving-tickets
Command: npx skills add https://github.com/dogkeeper886/ai-qa-workflow --skill receiving-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetches a Jira ticket with all linked tickets and Confluence pages, then creates a standardized project workspace folder with documentation files.

Core Features & Use Cases

  • Import ticket data (main, related, Confluence) into a project workspace.
  • Generate documentation files from ticket data.
  • Optional scaffolding to initialize test artifacts.

Quick Start

Run the receiving-tickets workflow to generate a standardized project workspace from a Jira ticket.

Frequently Asked Questions about receiving-tickets

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

FAQPage Schema
How do I automatically generate a project workspace from a Jira ticket?

To generate a project workspace from a Jira ticket, this Skill fetches the ticket data along with linked issues and assembles a standardized folder structure with documentation. It uses MCP tools to bootstrap folders and docs for immediate project setup.

Can I import Confluence pages and linked Jira issues into my project documentation?

Yes, you can import Confluence pages and linked Jira issues into project documentation. The workflow fetches main and related ticket data, then structures it into standardized documentation files within your project workspace.

What is the best way to bootstrap folders and test scaffolding from Jira tickets?

The best way to bootstrap folders and test scaffolding from Jira tickets is running the receiving-tickets workflow. It collects ticket data via MCP tools and optionally initializes test artifacts alongside the generated documentation.

Does this project setup workflow support ongoing Jira tickets or only new ones?

Yes, this project setup workflow supports both new and ongoing Jira tickets. Applying the workflow to existing tickets collects current data and structures it, ensuring the workspace remains ready for downstream automation tasks.

How does the MCP integration work for fetching Jira ticket data?

MCP integration works for fetching Jira ticket data by using MCP tools to collect main ticket details, linked issues, and Confluence pages. This mechanism ensures ticket data is structured and ready for downstream automation.

What are the limitations when creating documentation from Jira and Confluence data?

Limitations when creating documentation from Jira and Confluence data include relying entirely on MCP tool availability for fetching external data. The workspace generation depends on accessible ticket links and Confluence page permissions to assemble complete documentation.