jira

Solid

Unified Jira entry point. Routes to preview (default), create, or review subcommands.

Code & Development 40 stars 6 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
54
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Jira Single entry point for all Jira workflows: preview Draft tracks as Jira issues, create them via MCP (default = 1 Story per track; --epic = 1 Epic + 1-3 Stories), and review any Jira ticket (epic, story, bug, sub-task) end-to-end. ## Subcommand Routing Parse `$ARGUMENTS` and dispatch: | User Intent | Subcommand | Behavior | |-------------|------------|----------| | `(no args)`, `preview`, `preview <track-id>` | **preview** (default) | Generate `jira-export-<timestamp>.md` — **one Story** containing all phases/tasks | | `preview --epic ...` | **preview --epic** | Generate rich export: 1 Epic + 1–3 Stories (max) | | `create`, `create <track-id>` | **create** | Create **1 Story** (default) via MCP | | `review <JIRA_ID>` | **review** | Full qualification review of any Jira ticket — delegates to [references/review.md](references/review.md) | - `preview` is the default when no subcommand is supplied. - `review` requires a Jira ID as the next argument. Validate format `<PROJECT>-<NUMBER>` (e.g., `ENG-446236`). If numeric-only, prompt for project prefix — do NOT assume. --- ## Jira Configuration (Shared) All subcommands read project-level Jira configuration from `draft/workflow.md` under a `## Jira` section: ```markdown ## Jira Project Key: <KEY> Integration: jira-mcp Team: <team-name> Component: <component-name> Swimlane: <swimlane-name> Assignee Display Name: <assignee-name> ``` - **Project Key** — required for `create`. If missing, prompt and persist. - **Integra...

Details

Author
drafthq
Repository
drafthq/draft
Created
7 months ago
Last Updated
2 days ago
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

jira

Manage Jira issues, sprints, and epics with the jira CLI (ankitpokhrel/jira-cli). Trigger on: jira, jira-cli, ticket, issue key (e.g. PROJ-123), epic, sprint, transition/move ticket, comment on ticket, assign ticket, JQL, create bug/story, "what's on my board", "my open issues". Use when the user wants to find, read, create, update, transition, comment on, assign, or link Jira work items — or list sprints/epics — via CLI. Do not use for Todoist, GitHub Issues, Linear, or generic project planning with no Jira involvement.

1 Updated 3 days ago
tkolleh
AI & Automation Solid

jira

Manage Jira issues via CLI and REST. View, create, update, transition, assign, comment, and run sprint ops, including evidence follow-ups, native mentions, inline images, structured ADF comments, and board-column moves. Use when user mentions issue keys (PROJ-123), tickets, follow-ups, sprints, or keywords like jira/ticket/backlog.

5 Updated 2 days ago
vanducng
AI & Automation Listed

jira-review

Reviews Jira issues for implementation readiness. Detects complexity signals, parses acceptance criteria, and recommends clarification or planning mode when needed. Use when reviewing a Jira issue for readiness, checking whether a ticket has enough detail to implement, assessing acceptance-criteria completeness, or evaluating a story before sprint planning. Not for completed implementations (reviews readiness, not accuracy), or non-Jira trackers.

2 Updated 1 weeks ago
michaelalber