Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    meeting notes to tickets

    2

    Converts messy meeting notes and transcripts into prioritized, implementation-ready tickets for Jira, Linear, and GitHub.

    $14.99

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    meeting notes to tickets

    meeting notes to tickets

    Example session with this skill installed

    Extract actionable engineering work from these notes for Jira:
    'Discussed the auth bug. Sarah said we need to fix the JWT expiry issues by Friday. We also talked about adding a dark mode toggle, but didn't decide on the colors yet. Mike will handle the auth fix.'

    • Read your context and instructions
    • Compiled the meeting notes to

    I have analyzed the notes and extracted the actionable engineering work.

    Ticket Extraction

    Summary

    • Tickets identified: 1
    • P0: 1 P1: 0 P2: 0 P3: 0
    • Ambiguous items requiring review: 1

    Ticket 1 — Fix JWT Expiration Issues
    Type: Bug
    Priority: P0 (Target: Friday)
    Effort: M — confidence low
    Owner: Mike
    Dependencies: None identified

    Description

    Resolve reported issues with JWT token expiration to ensure user sessions are handled correctly according to the timeline discussed.

    Acceptance Criteria

    • Given a user has an active session, when the JWT expires, the system must trigger a silent refresh or redirect to login.
    • The expiration logic must align with the security requirements discussed for the Friday deadline.
    • Implementation must be verified across both web and mobile clients.

    Why This Matters

    Fixing the auth bug reduces session-related errors and is critical for the upcoming release deadline.

    ⚠️ Items Requiring Clarification

    Dark Mode Toggle: The feature was discussed but lacked a final decision on color palettes and design specs. No ticket was created to avoid guesswork.

    Next steps

    1. Copy the "Fix JWT Expiration Issues" block directly into your Jira Create Issue screen.
    2. Assign the ticket to Mike.
    3. Follow up with the design team regarding the dark mode color palette before creating a UI ticket.

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

    What you get

    Extract testable acceptance criteria from raw meeting transcripts.Convert customer discovery calls into structured Jira bug reports.Identify and flag ambiguous requirements that need further team discussion.Format implementation-ready tickets for Linear, GitHub, and Notion.

    About this skill

    The problem

    Meeting transcripts and notes are often a disorganized mess of ideas, sidebars, and half-formed plans. Converting these into actionable tickets manually is a tedious task that risks missing critical dependencies or inventing requirements to fill gaps.

    What it does

    • Identifies implementation-ready work from raw voice-to-text, Slack dumps, or informal notes.
    • Standardizes output for Linear, Jira, GitHub Issues, and Notion with paste-ready formatting.
    • Generates testable acceptance criteria using Given/When/Then or behavioral statements.
    • Flags ambiguity and missing context instead of guessing developer requirements.
    • Redacts sensitive personal, medical, or HR information from operational tickets.

    Why this beats prompting it yourself

    Generic prompts often hallucinate missing details or turn every sentence into a useless ticket. This tool uses a multi-phase extraction process that merges duplicates, distinguishes inferred priorities from explicit ones, and enforces an "Ambiguity Gate" to ensure high-signal output.

    Use cases

    • Converting a messy founder-led brainstorming session into a prioritized GitHub project.
    • Turning a customer call recording into specific bug reports and feature requests.
    • Extracting actionable engineering tasks from daily standup notes.
    • Standardizing team handoffs by generating tickets with clear owners and dependencies.

    Known limitations

    Does not file tickets directly into external systems without a connected tool. Effort estimates are relative (S/M/L) and not precise time guarantees.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 6 days ago

    • Passed all security checks, Safe to install

    Listed6 days ago
    Updated1 day ago

    Frequently Asked Questions