All tutorials
15 minintermediate

Turn Meeting Notes into Jira Tickets

Paste your messy meeting notes. Get structured tickets with acceptance criteria. Never transcribe by hand again.

Every PM has been there. You walk out of a meeting with a page of messy notes and spend the next hour turning them into Jira tickets. Let's automate that. You'll create a skill that takes raw meeting notes and outputs clean, structured tickets ready to file.

1

Set up a CLAUDE.md with PM context

Start by giving Claude some context about your work. You don't need much — just enough so it knows what kind of tickets you create.

bash
cat > CLAUDE.md << 'EOF'
# CLAUDE.md

## Role
Product Manager workspace. I manage a SaaS product with a web app and mobile app.

## Ticket Format
- All tickets go to Jira project KEY
- Use story points: 1, 2, 3, 5, 8
- Include acceptance criteria as checkboxes
- Tag with team labels: frontend, backend, design, mobile

## My Team
- Frontend: React/Next.js
- Backend: Node.js/PostgreSQL
- Mobile: React Native
EOF
PM workspace setup
2

Create the meeting processor skill

This skill tells Claude exactly how to parse meeting notes. It extracts action items, decides who owns them, estimates effort, and formats them as tickets.

bash
mkdir -p .claude/skills
cat > .claude/skills/meeting-to-tickets.md << 'EOF'
# Meeting to Tickets Skill

When given meeting notes, extract action items and convert them to structured tickets.

## Process
1. Read the raw meeting notes
2. Identify every action item, decision, and follow-up
3. Group related items into logical tickets
4. Estimate story points based on complexity
5. Assign team labels based on the work involved

## Output Format
For each ticket:

### [TICKET-TITLE]
**Type**: Story | Bug | Task
**Points**: 1 | 2 | 3 | 5 | 8
**Labels**: frontend, backend, design, mobile
**Description**: One paragraph explaining the work.

**Acceptance Criteria**:
- [ ] First criteria
- [ ] Second criteria
- [ ] Third criteria

## Rules
- One ticket per discrete piece of work
- Don't combine unrelated items
- If something is vague, flag it as "needs clarification"
- Default to 3 points if effort is unclear
- Always include at least 3 acceptance criteria
EOF
Skill created
3

Paste messy meeting notes

Here's the real test. Paste some actual messy meeting notes (or use these sample ones) and watch Claude turn chaos into structure.

bash
claude "Process these meeting notes into tickets:

Sprint planning - March 29
---
sarah mentioned the checkout flow is broken on mobile again,
users can't tap the pay button. also we need to add apple pay
before Q2. jake said the API is too slow on the product listing
page - takes 3 seconds. we agreed to add caching. oh and
marketing wants a banner on the homepage for the spring sale,
needs to be up by friday. also someone should update the
onboarding flow - users are dropping off at step 3."
Messy notes in, clean tickets out
4

Review the structured output

Claude gives you fully formed tickets with types, story points, labels, and acceptance criteria. Each one is ready to paste into Jira. No more staring at your notes trying to remember what was decided.

What you get
5

Optional: Connect an MCP for auto-creation

If you want to go further, you can connect a GitHub or Linear MCP server so Claude can create the tickets directly. No copy-paste needed.

json
# Add to your .mcp.json to enable GitHub Issues:
{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_TOKEN": "your-token-here"
      }
    }
  }
}
Auto-creation with MCP

What's next?

Explore the full PM workflow guide

Stay in the loop

New guides, templates, and tips. No spam. Unsubscribe anytime.