jira-draft

Draft Jira issues as local Markdown files with YAML frontmatter.

2|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/jimweller/davit-dataops-dotfiles --skill jira-draft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-draft
Source: https://github.com/jimweller/davit-dataops-dotfiles/tree/main/dataops-plugin/skills/jira-draft
Command: npx skills add https://github.com/jimweller/davit-dataops-dotfiles --skill jira-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows users to draft Jira issues locally as Markdown files, ensuring content quality and consistency before any interaction with Jira, preventing accidental creation or modification of live issues.

Core Features & Use Cases

  • Local Draft Creation: Generates .md files in a .jira-drafts/ directory for review.
  • Structured Content: Enforces clear CONTEXT, Requirements, and Acceptance Criteria patterns.
  • Metadata Management: Handles frontmatter for issue type, project, assignee, links, and more.
  • Use Case: A developer needs to create a detailed bug report. They use this Skill to draft the report locally, including steps to reproduce, expected vs. actual behavior, and relevant logs, ensuring all necessary information is present before publishing.

Quick Start

Use the jira-draft skill to create a new story issue for setting up a dedicated OpenAI instance for CMS, assigning it to [email protected] under epic PE-100.

Frequently Asked Questions about jira-draft

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

FAQPage Schema
How do I draft Jira issues locally without touching the live Jira instance?

Draft Jira issues locally by generating structured markdown files with YAML frontmatter for metadata and body text for requirements. This approach manages issue creation, updates, and comments entirely offline, ensuring content quality before publishing.

What is the best way to manage issue metadata for a Jira draft?

Manage issue metadata using structured YAML frontmatter within local markdown files. This method handles issue type, project, assignee, components, labels, and links, adhering to defined content principles before any publishing occurs.

How do I structure a bug report for Jira using markdown?

Structure a bug report in markdown by enforcing clear CONTEXT, Requirements, and Acceptance Criteria patterns. Include steps to reproduce, expected versus actual behavior, and relevant logs to ensure all necessary information is present.

Does jira-draft support direct interaction with Jira for issue creation?

No, jira-draft enforces a strict rule against direct Jira interaction. It drafts issue content into local markdown files within a dedicated directory for review, preventing accidental creation or modification of live issues.

Can I use markdown to update existing Jira issues and comments?

Yes, manage issue updates and comments via structured YAML frontmatter and markdown body text. Draft these changes locally to review content and metadata before publishing them to Jira.

Why should I draft Jira content locally instead of writing directly in Jira?

Drafting Jira content locally ensures content quality and consistency before any interaction with Jira. This process prevents accidental creation or modification of live issues by reviewing structured markdown files first.