skills.rest
mayurpise
mayurpiseCOMMUNITY
Explore all skills by this author →
Website𝕏@mayurpiseGitHub

jira-preview

Generate a Jira export file from a track plan for review.

39|6|Updated Jan 21, 2026
Search Tags:#automation#review#jira#export#project-management#track plan
One-click install
npx skills add https://github.com/mayurpise/draft --skill jira-preview
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-preview
Source: https://github.com/mayurpise/draft/tree/main/skills/jira-preview
Command: npx skills add https://github.com/mayurpise/draft --skill jira-preview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to preview Jira issues derived from a track plan before creating actual Jira issues, reducing misalignment and rework.

Core Features & Use Cases

  • Jira export generation: Converts track plan data into a Jira-ready jira-export.md with Epic, Stories, and Sub-tasks mapping.
  • Preview & validation: Lets stakeholders review the generated export, adjust descriptions, and confirm task scope before creation.
  • Workflow alignment: Automatically reads track metadata (title/type), plan phases, and tasks to ensure Jira entries reflect the plan accurately.

Quick Start

  • Run the jira-preview action to generate draft/tracks/<track_id>/jira-export.md from the active track.
  • Review and edit jira-export.md, then run /draft:jira-create to publish issues to Jira.

Frequently Asked Questions about jira-preview

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

FAQPage Schema
How do I preview Jira issues before creating them from a track plan?▼

You can generate a Jira export markdown file from a track plan to review Epics, Stories, and Sub-tasks before creating actual Jira issues, reducing misalignment and rework.

How does converting a track plan to Jira Epics and Stories work?▼

Converting a track plan to Jira issues works by reading track metadata, plan phases, and tasks, then mapping them into Jira-ready Epics, Stories, and Sub-tasks within a markdown export file.

What's the best way to validate Jira task scope against a project plan?▼

The best way to validate Jira task scope is to generate a Jira export file from your draft track plan, review the mapped Epics and Stories, and adjust descriptions before publishing issues to Jira.

What files do I need to generate a Jira export from a track plan?▼

Generating a Jira export requires track metadata files including draft/tracks.md, plan.md, metadata.json, spec.md, and core/templates/jira.md to accurately map plan phases into Jira issues.

Can I edit the Jira export file before publishing issues to Jira?▼

Yes, you can review and edit the generated jira-export.md file to adjust descriptions and confirm task scope before running the final action to publish issues directly to Jira.

When should I avoid generating a Jira export from a track plan?▼

You should avoid generating a Jira export if your track plan lacks defined phases and tasks, as the process relies on reading structured plan data to map Jira Epics, Stories, and Sub-tasks accurately.

Related Skills

Explore More Product & Management Skills→
mayurpisemayurpise
39

jira-create

Create Epic, Stories, and Sub-tasks in Jira from a jira-export.md file via MCP-Jira.

Community
Advanced
dasheck0dasheck0
8

epic-to-stories

Convert Jira Epics into testable user stories with acceptance criteria.

Community
Advanced
salarogliosalaroglio
5

mde-jira-triage

Triage Jira issues and draft a Markdown implementation plan.

Community
Intermediate
TUP-TESIS-LABTUP-TESIS-LAB
1

jira-workflow

Create and synchronize Jira issues from planning documents using jira-cli.

Official
Advanced