Analyze meeting notes to find action items and create Jira tasks for assigned work. When an agent needs to: (1) Create Jira tasks or tickets from meeting notes, (2) Extract or find action items from notes or Confluence pages, (3) Parse meeting notes for assigned tasks, or (4) Analyze notes and generate tasks for team members. Identifies assignees, looks up account IDs, and creates tasks with proper context.
meeting notes, action items, create tasks, create tickets, extract tasks, parse notes, analyze notes, assigned work, assignees, from meeting, post-meeting, capture tasks, generate tasks, turn into tasks, convert to tasks, action item, to-do, task list, follow-up, assigned to, create Jira tasks, create Jira tickets, meeting action items, extract action items, find action items, analyze meeting
Automatically extract action items from meeting notes and create Jira tasks with proper assignees. This skill parses unstructured meeting notes (from Confluence or pasted text), identifies action items with assignees, looks up Jira account IDs, and creates tasks—eliminating the tedious post-meeting ticket creation process.
Use this skill when: Users have meeting notes with action items that need to become Jira tasks.
Follow this 7-step process to turn meeting notes into actionable Jira tasks:
Obtain the meeting notes from the user.
If user provides a Confluence URL:
getConfluencePage(
cloudId="...",
pageId="[extracted from URL]",
contentFormat="markdown"
)
URL patterns:
https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]getAccessibleAtlassianResourcesIf user pastes meeting notes directly:
Ask: "Do you have a Confluence link to the meeting notes, or would you like to paste them directly?"
Scan the notes for action items with assignees.
Pattern 1: @mention format (highest priority)
@Sarah to create user stories for chat feature
@Mike will update architecture doc
Pattern 2: Name + action verb
Sarah to create user stories
Mike will update architecture doc
Lisa should review the mockups
Pattern 3: Action: Name - Task
Action: Sarah - create user stories
Action Item: Mike - update architecture
Pattern 4: TODO with assignee
TODO: Create user stories (Sarah)
TODO: Update docs - Mike
Pattern 5: Bullet with name
- Sarah: create user stories
- Mike - update architecture
For each action item, extract:
Assignee Name
Task Description
Context (optional but helpful)
Input:
# Product Planning - Dec 3
Action Items:
- @Sarah to create user stories for chat feature
- Mike will update the architecture doc
- Lisa: review and approve design mockups
Parsed:
1. Assignee: Sarah
Task: Create user stories for chat feature
Context: Product Planning meeting - Dec 3
2. Assignee: Mike
Task: Update the architecture doc
Context: Product Planning meeting - Dec 3
3. Assignee: Lisa
Task: Review and approve design mockups
Context: Product Planning meeting - Dec 3
Before looking up users or creating tasks, identify the Jira project.
Ask: "Which Jira project should I create these tasks in? (e.g., PROJ, PRODUCT, ENG)"
Call getVisibleJiraProjects to show options:
getVisibleJiraProjects(
cloudId="...",
action="create"
)
Present: "I found these projects you can create tasks in: PROJ (Project Alpha), PRODUCT (Product Team), ENG (Engineering)"
For each assignee name, find their Jira account ID.
lookupJiraAccountId(
cloudId="...",
searchString="[assignee name]"
)
The search string can be:
Scenario A: Exact Match (1 result)
✅ Found: Sarah Johnson ([email protected])
→ Use accountId from result
Scenario B: No Match (0 results)
⚠️ Couldn't find user "Sarah" in Jira.
Options:
1. Create task unassigned (assign manually later)
2. Skip this task
3. Try different name format (e.g., "Sarah Johnson")
Which would you prefer?
Scenario C: Multiple Matches (2+ results)
⚠️ Found multiple users named "Sarah":
1. Sarah Johnson ([email protected])
2. Sarah Smith ([email protected])
Which user should be assigned the task "Create user stories"?
CRITICAL: Always show the parsed action items to the user BEFORE creating any tasks.
I found [N] action items from the meeting notes. Should I create these Jira tasks in [PROJECT]?
1. [TASK] [Task description]
Assigned to: [Name] ([email if found])
Context: [Meeting title/date]
2. [TASK] [Task description]
Assigned to: [Name] ([email if found])
Context: [Meeting title/date]
[...continue for all tasks...]
Would you like me to:
1. Create all tasks
2. Skip some tasks (which ones?)
3. Modify any descriptions or assignees
Do NOT create tasks until user confirms. Options:
Once confirmed, create each Jira task.
Before creating tasks, check what issue types are available in the project:
getJiraProjectIssueTypesMetadata(
cloudId="...",
projectIdOrKey="PROJ"
)
Choose the appropriate issue type:
createJiraIssue(
cloudId="...",
projectKey="PROJ",
issueTypeName="[Task or available type]",
summary="[Task description]",
description="[Full description with context]",
assignee_account_id="[looked up account ID]"
)
Use action verbs and be specific:
**Action Item from Meeting Notes**
**Task:** [Original action item text]
**Context:**
[Meeting title/date]
[Relevant discussion points or decisions]
**Source:** [Link to Confluence meeting notes if available]
**Original Note:**
> [Exact quote from meeting notes]
Example:
**Action Item from Meeting Notes**
**Task:** Create user stories for chat feature
**Context:**
Product Planning Meeting - December 3, 2025
Discussed Q1 roadmap priorities and new feature requirements
**Source:** https://yoursite.atlassian.net/wiki/spaces/TEAM/pages/12345
**Original Note:**
> @Sarah to create user stories for chat feature
After all tasks are created, present a comprehensive summary.
Format:
✅ Created [N] tasks in [PROJECT]:
1. [PROJ-123] - [Task summary]
Assigned to: [Name]
https://yoursite.atlassian.net/browse/PROJ-123
2. [PROJ-124] - [Task summary]
Assigned to: [Name]
https://yoursite.atlassian.net/browse/PROJ-124
[...continue for all created tasks...]
**Source:** [Link to meeting notes]
**Next Steps:**
- Review tasks in Jira for accuracy
- Add any additional details or attachments
- Adjust priorities if needed
- Link related tickets if applicable
@john to update documentation
@sarah will create the report
@mike should review PR #123
Parsed:
John to update documentation
Sarah will create the report
Mike should review PR #123
Lisa needs to test the feature
Parsed:
Action: John - update documentation
Action Item: Sarah - create the report
AI: Mike - review PR #123
Parsed:
TODO: Update documentation (John)
TODO: Create report - Sarah
[ ] Mike: review PR #123
Parsed:
- John: update documentation
- Sarah - create the report
* Mike will review PR #123
Parsed:
If no action items with assignees are detected:
I analyzed the meeting notes but couldn't find any action items with clear assignees.
Action items typically follow patterns like:
- @Name to do X
- Name will do X
- Action: Name - do X
- TODO: X (Name)
Options:
1. I can search for TODO items without assignees
2. You can point out specific action items to create
3. I can create tasks for bullet points you specify
What would you like to do?
If some action items have assignees and some don't:
I found [N] action items:
- [X] with clear assignees
- [Y] without assignees
Should I:
1. Create all [N] tasks ([X] assigned, [Y] unassigned)
2. Only create the [X] tasks with assignees
3. Ask you to assign the [Y] unassigned tasks
Which option would you prefer?
If the same person is mentioned different ways:
Notes mention: @sarah, Sarah, Sarah J.
These likely refer to the same person. I'll look up "Sarah" once and use
that account ID for all three mentions. Is that correct?
If the same task appears multiple times:
I found what appears to be the same action item twice:
1. "@Sarah to create user stories" (line 15)
2. "Action: Sarah - create user stories" (line 42)
Should I:
1. Create one task (combine duplicates)
2. Create two separate tasks
3. Skip the duplicate
What would you prefer?
If action item text is very long (>200 characters):
The task "[long text...]" is quite detailed.
Should I:
1. Use first sentence as summary, rest in description
2. Use full text as summary
3. Let you edit it to be more concise
Which would you prefer?
✅ Use consistent @mention format in notes
✅ Include full names when possible
✅ Be specific in action item descriptions
✅ Add context (why/what/when)
✅ Review parsed tasks before confirming
❌ Mix multiple tasks for one person in one bullet
❌ Use ambiguous names (just "John" if you have 5 Johns)
❌ Skip action verbs (unclear what to do)
❌ Forget to specify project
# Meeting Title - Date
Attendees: [Names]
## Decisions
[What was decided]
## Action Items
- @FullName to [specific task with context]
- @AnotherPerson will [specific task with context]
- etc.
This skill is for converting meeting action items to Jira tasks only.
Don't use for:
❌ Summarizing meetings (no task creation)
❌ Finding meeting notes (use search skill)
❌ Creating calendar events
❌ Sending meeting notes via email
❌ General note-taking
Use only when: Meeting notes exist and action items need to become Jira tasks.
Input:
Team Sync - Dec 3, 2025
Action Items:
- @Sarah to create user stories for chat feature
- @Mike will update the architecture doc
- @Lisa should review design mockups
Process:
Output:
✅ Created 3 tasks in PROJ:
1. PROJ-100 - Create user stories for chat feature
Assigned to: Sarah Johnson
2. PROJ-101 - Update the architecture doc
Assigned to: Mike Chen
3. PROJ-102 - Review design mockups
Assigned to: Lisa Park
Input:
Product Review Meeting
Discussed new features and priorities.
Follow-ups:
- Sarah will draft the PRD
- Mike: implement API changes
- TODO: Review security audit (Lisa)
- Update stakeholders on timeline
Process:
Input:
Sprint Planning
Action Items:
- @John to update tests
- @Sarah to refactor code
Process:
Primary tool: getConfluencePage (if URL) or use pasted text
Account lookup: lookupJiraAccountId(searchString)
Task creation: createJiraIssue with assignee_account_id
Action patterns to look for:
@Name to/will/should XName to/will/should XAction: Name - XTODO: X (Name)Name: XAlways:
Remember: