Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Requirements-to-Jira Skills

    1

    Transform messy transcripts and notes into traceable, Jira-ready user stories while flagging gaps and contradictions.

    Free

    Security scanned
    Requirements-to-Jira Skills

    Requirements-to-Jira Skills

    Example session with this skill installed

    Convert these notes from the workshop into user stories. We use Jira project key 'PAY'.
    Note 1 (Devin): The user needs to see their balance on the home screen.
    Note 2 (Sarah): Actually, they should only see the balance after clicking a 'View' button for privacy.
    Note 3: The app must be super fast.

    • Read your context and instructions
    • Compiled the requirements-to-jira

    I have analyzed the workshop notes (Source A). I identified one conflicting requirement regarding balance visibility and one vague requirement regarding performance.

    Summary

    • Sources: 1
    • Stories: 1 (1 Blocked)
    • Conflicts: 1
    • Vague Requirements: 1
    • Unowned Items: 0
    • Gaps: 1

    Decisions needed

    1. Conflict (S-01): Decide if the balance is visible immediately (Devin, A-1) or requires a click (Sarah, A-2).
    2. Vague Requirement: Define the specific latency threshold for "super fast" (A-3).

    User stories

    PAY-01: View account balance
    As a user, I want to see my account balance, so that I know my available funds.

    • Given the user is on the home screen, when they [action to be decided], then the account balance is displayed.

    Priority (proposed): Must. Source: [A Devin, A Sarah]. Status: Blocked. Notes: Conflict between immediate visibility vs. click-to-view.

    Conflicts

    Conflict 1: Note 1 (Devin) states balance is on home screen; Note 2 (Sarah) requires a 'View' button click for privacy.

    • Decision needed: Confirm UI pattern for privacy. Owner: [not stated].

    Vague requirements

    • "Super fast": This is not testable.
    • Clarification: What is the maximum acceptable load time in milliseconds? At what percentile (e.g., p95)?

    Gaps and assumptions

    • [not stated]: The specific currency or format for the balance display is not mentioned.

    Jira CSV

    "Summary","Issue Type","Description","Priority","Labels"
    "PAY-01: View account balance","Story","As a user, I want to see my account balance, so that I know my available funds.
    
    Acceptance criteria:
    1. Given the user is on the home screen, when they [action to be decided], then the account balance is displayed.
    
    Notes: Conflict between immediate visibility vs. click-to-view. [not stated] display format.
    Status: Blocked
    Source: [A Devin, A Sarah]","High","needs-decision"
    

    Next steps

    1. Resolve the visibility conflict between Devin and Sarah.
    2. Define "super fast" with a specific performance metric.
    3. Import the provided CSV into your Jira project.

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

    About this skill

    The problem

    Business analysts and project managers spend hours turning meeting transcripts, email threads and half-written BRDs into stories. Typing is not the real risk. The real risk is what gets missed: two stakeholders asking for incompatible things, a requirement like “it should be fast” that nobody can test, and a decision everyone agrees is needed but nobody owns. Those problems surface late and cost the most.

    What I built

    The story-drafter(Requirements-to-Jira ) Skill Given raw sources, it:

    extracts every stated requirement and merges duplicates across sources; writes user stories with testable acceptance criteria, a proposed priority and a status (Ready, Needs confirmation or Blocked); flags contradictions between sources, vague requirements (with the clarifying questions to ask) and unowned decisions, and keeps affected stories separate instead of silently picking a side; cites the exact source line for every requirement, and writes [not stated] instead of inventing numbers, owners or dates; produces a Decisions needed list for stakeholders and a Jira import file.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.

    Cannot invent technical specs or edge cases not in the source. Requires clear source references (timestamps/sections) to maintain traceability. CSV generation requires Python execution environment.

    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 buying a skill.

    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

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 11 days ago

    • Free with an Agensi account

    Permissions

    Read Files
    Write Files
    Listed11 days ago

    What's inside

    Frequently Asked Questions

    The skill requires text-based inputs such as Zoom/Teams transcripts, email threads, or raw meeting notes. It works best when sources are clearly separated so it can maintain accurate traceability for every acceptance criterion.

    Unlike generic AI prompts that fill in blanks with 'hallucinations,' this skill flags missing information as '[not stated]' and highlights contradictions. This ensures your Jira tickets are based entirely on stakeholder facts rather than AI-invented requirements.

    The skill generates a Jira-compatible CSV file and Gherkin-formatted text. You can use the standard Jira 'External System Import' tool to bulk-upload these stories, including pre-mapped summaries, descriptions, and priorities.

    No complex setup is required; once added to your AI agent, you simply provide your raw notes. The skill is compatible with most leading LLM agents that support file processing or long-form text analysis.

    The skill will identify the conflict and flag it as a 'Required Resolution' instead of choosing one side. It provides you with the specific source references for both conflicting points so you can make an informed final decision.

    Your purchase includes the specialized skill logic, the Gherkin-formatting engine, and the CSV export utility. Buyers receive all future logic updates and refinements to the requirement-filtering criteria at no extra cost.

    New in Business & Operations

    Free