Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Jira Ticket Intake

    1

    Load and normalize Jira ticket data, acceptance criteria, and dependency context into structured JSON for developers.

    $4.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Jira Ticket Intake

    Jira Ticket Intake

    Example session with this skill installed

    Run jira-ticket-intake for PROJ-104. We need to know the AC and if the backend dependency PROJ-59 is actually finished.

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

    I have fetched the full context for PROJ-104 from Jira. The ticket is currently in 'To Do' and is blocked by PROJ-59, which is marked as 'Done'. I have included the technical context from PROJ-59 regarding the new schema changes in the output below.

    implementationContext

    {
      "issueKey": "PROJ-104",
      "summary": "Implement user profile API endpoint",
      "description": "Create a new REST endpoint to fetch user profile data including preferences.",
      "acceptanceCriteria": [
        "GET /api/v1/profile returns 200 OK",
        "Response includes user preferences object",
        "Unauthorized requests return 401"
      ],
      "issueType": "Story",
      "status": "To Do",
      "priority": "High",
      "labels": ["backend", "api"],
      "fixVersions": ["Sprint 14"],
      "parentEpic": {
        "key": "PROJ-100",
        "summary": "User Management Service",
        "status": "In Progress"
      },
      "links": [
        {
          "type": "Blocks",
          "direction": "is blocked by",
          "key": "PROJ-59",
          "summary": "Database schema migration for user preferences",
          "status": "Done"
        }
      ],
      "completedDependencies": [
        {
          "key": "PROJ-59",
          "summary": "Database schema migration for user preferences",
          "relevantContext": "Added 'preferences' JSONB column to 'users' table. Requires standard DB connection."
        }
      ],
      "comments": [
        {
          "author": "jane.doe",
          "summary": "Confirmed we should use JSONB for the preferences field to allow flexibility."
        }
      ],
      "source": "jira",
      "verificationNote": "Ticket claims only - not verified against the current repository state. Run repository-investigation before acting on any of this."
    }
    

    Next steps

    1. Run repository-investigation to locate the existing user service and DB models.
    2. Verify the schema changes mentioned in PROJ-59 exist in the current branch.
    3. Create a new branch feature/PROJ-104-user-profile-api.

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

    About this skill

    Developers often waste time context-switching between their IDE and Jira, leading to missing acceptance criteria or building on top of unresolved dependencies. This skill extracts and normalizes the full work context from Jira into a structured format before a single line of code is written.

    What it does

    • Work Context Extraction fetches the summary, description, and metadata for a specific issue key.
    • AC Parsing isolates acceptance criteria from raw description text for clear validation.
    • Dependency Analysis identifies blockers and fetches technical context from completed parent or linked tasks.
    • Epic Mapping links the issue to its parent Epic to provide broader project vision.
    • Comment Summarization filters out system noise to highlight substantive stakeholder decisions and scope changes.

    How it works

    1. Trigger the skill by providing a valid Jira issue key like PROJ-104.
    2. The agent uses Atlassian MCP tools to query the issue, its links, and its parent Epic.
    3. It recursively fetches context for completed dependencies that shape the current implementation.
    4. It outputs a standardized implementationContext JSON object for use by subsequent development skills.

    Frameworks & tools

    This skill requires authenticated Jira MCP tools (mcp__atlassian__*) and works within any environment supporting MCP, such as Claude Code or Cursor.

    Why this beats prompting it yourself

    Generic prompts often miss the nuances of issue links or bury acceptance criteria in unstructured text blocks. This skill enforces a strict output contract that separates "what Jira says" from "what the code does," preventing hallucinated requirements and identifying blockers before you branch.

    Use cases

    • Task Kickoff to gather all requirements before starting repository investigation.
    • Blocker Identification to verify if a ticket is actually ready for development.
    • Sprint Transitions to re-sync context when a ticket's criteria change mid-work.
    • Technical Context Gathering to see implementation details from recently closed PRs linked to the ticket.

    Known limitations

    Requires pre-configured and authenticated Jira MCP access. It only reads data and will not transition tickets or post comments.

    Requires authenticated Jira MCP tools. Read-only; cannot mutate Jira state. Does not verify repository state.

    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 MCP

    Permissions

    Network Access

    Allowed Hosts

    atlassian.com

    Read-only — never writes to Jira, never touches local files.

    Listed18 days ago

    What's inside

    Frequently Asked Questions

    This skill extracts and normalizes Jira data—including acceptance criteria, dependency status, and epic context—into a structured JSON format to prevent developers from missing critical requirements or building on blocked tasks.

    It is compatible with any AI environment that supports Model Context Protocol (MCP), including Claude Code and Cursor, provided you have the Atlassian MCP tools authenticated.

    No, this is a read-only context gathering tool; it focuses on providing accurate implementation data and will not modify ticket statuses or add comments to your Jira board.

    You will need a valid Jira instance and the Atlassian MCP connector configured with your API credentials so the agent can securely query your project data.

    The skill recursively analyzes linked issues to identify blockers and fetches technical context from completed parent tasks, ensuring you understand the architectural foundations before coding.

    You receive the structured logic and schema definitions required to generate the `implementationContext` JSON, along with updates to ensure compatibility with evolving Jira API standards.

    New in Business & Operations