Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Jira Ticket Authoring

    1

    Turns an approved requirement into a well-structured Jira ticket — checks for duplicates and the right parent epic first.

    $4.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Jira Ticket Authoring

    Jira Ticket Authoring

    Example session with this skill installed

    We should rate-limit our outbound email sends — if our email provider starts failing, we keep retrying and burn through our whole send budget in a retry storm. Can you track this as a ticket?

    • Read your context and instructions
    • Compiled the jira ticket authoring

    Summary

    Checked for duplicates and the right Epic before creating anything — found two related tickets that don't actually cover this, matched the correct Epic, and staged a new ticket for your approval. Nothing was created yet.

    StepResult
    Duplicate check2 related tickets found (budget guardrails, provider fallback) — neither covers rate-limiting itself
    Epic matchMessaging Platform Core
    Labelsmessaging-core, reliability (reused from sibling tickets)
    StatusStaged draft — awaiting your approval
    {
      "action": "created",
      "issue": {
        "key": "PROJ-131",
        "summary": "Add outbound rate limiting/backoff for email provider sends",
        "issueType": "Task",
        "parentEpic": { "key": "PROJ-10", "summary": "Messaging Platform Core" },
        "priority": "Medium",
        "labels": ["messaging-core", "reliability"]
      },
      "unresolvedFields": ["fixVersion - not stated, left unset"],
      "awaitingApproval": true
    }
    

    Next steps

    • Review the staged ticket above
    • Say the word to approve — only then does it actually get created in Jira

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Stops ticket sprawl before it starts. Given a requirement in plain words, this skill searches your Jira project for exact duplicates and related-but-distinct work before anything gets created, matches it to the right parent Epic using your project's own existing conventions (not invented rules), and drafts a complete, well-structured ticket — Context, Goal, Scope, Acceptance Criteria, Dependencies — ready for a coding agent or a human to pick up.

    It never creates or edits a Jira issue without your explicit approval first — every result is a staged draft you review.

    Part of the Ticket-to-Shipped workflow: 10 skills covering the full requirement-to-shipped-code lifecycle. Works standalone too.

    Expects a Jira MCP integration (e.g. Atlassian MCP) to already be connected and authenticated in your agent — it doesn't set that up for you. Built and tested against Jira specifically; adapting it to Linear, GitHub Issues, or another tracker would need changes to the MCP calls. Relies on your project already having some consistent conventions (issue types, labels, Epics) to match against — in a brand-new, empty Jira project with no existing tickets, it has nothing to pattern-match from and will fall back to asking rather than guessing.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 18 days ago

    Requires

    Atlassian
    Jira
    Git

    Permissions

    Network Access

    Allowed Hosts

    atlassian.com
    jira.com

    Only reads and writes Jira issues via MCP tools. Never touches the local filesystem. Every issue creation or edit is staged as a draft and requires explicit human approval before it's actually written to Jira.

    Listed18 days ago

    What's inside

    Frequently Asked Questions

    Not out of the box — it's built around Jira's MCP tools specifically. The underlying logic (duplicate-check, Epic-matching, structured ticket format) could be adapted to Linear or GitHub Issues, but this version expects Jira's API shape.

    No. Every result is a staged draft — duplicate check, Epic match, and full ticket content — that requires your explicit approval before anything is actually created or edited in Jira.

    It proceeds without a parent Epic when none fits rather than forcing one. If no Epic matches at all, it flags that a new Epic might be needed and stops for a human to decide — it never creates an Epic on its own.

    New in Business & Operations