capture-tasks-from-meeting-notes

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Capture Tasks from Meeting Notes

从会议记录中捕获任务

Keywords

关键词

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

会议记录, 行动项, 创建任务, 创建工单, 提取任务, 解析记录, 分析记录, 已分配工作, 经办人, 来自会议, 会后工作, 捕获任务, 生成任务, 转换为任务, 行动项, 待办事项, 任务列表, 跟进事项, 分配给, 创建Jira任务, 创建Jira工单, 会议行动项, 提取行动项, 查找行动项, 分析会议

Overview

概述

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.

自动从会议记录中提取行动项，并为其分配合适的经办人以创建Jira任务。该技能可解析非结构化会议记录（来自Confluence或粘贴的文本），识别带有经办人的行动项，查询Jira账号ID并创建任务——省去了繁琐的会后工单创建流程。

适用场景： 用户拥有包含行动项的会议记录，需要将其转换为Jira任务时。

Workflow

工作流程

Follow this 7-step process to turn meeting notes into actionable Jira tasks:

按照以下7个步骤将会议记录转换为可执行的Jira任务：

Step 1: Get Meeting Notes

步骤1：获取会议记录

Obtain the meeting notes from the user.

从用户处获取会议记录。

Option A: Confluence Page URL

选项A：Confluence页面URL

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]

Extract PAGE_ID from the numeric portion
Get cloudId from site name or use
```
getAccessibleAtlassianResources
```

如果用户提供Confluence URL：

getConfluencePage(
  cloudId="...",
  pageId="[从URL中提取]",
  contentFormat="markdown"
)

URL格式：

https://[站点].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[标题]

从URL的数字部分提取PAGE_ID
从站点名称获取cloudId，或调用
```
getAccessibleAtlassianResources
```
获取

Option B: Pasted Text

选项B：粘贴文本

If user pastes meeting notes directly:

Use the text as-is
No fetching needed

如果用户直接粘贴会议记录：

直接使用该文本
无需调用接口获取

If Unclear

若信息不明确

Ask: "Do you have a Confluence link to the meeting notes, or would you like to paste them directly?"

询问：“你是否有会议记录的Confluence链接，还是直接粘贴记录内容？”

Step 2: Parse Action Items

步骤2：解析行动项

Scan the notes for action items with assignees.

扫描会议记录，找出带有经办人的行动项。

Common Patterns

常见格式

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

格式1：@提及格式（优先级最高）

@Sarah to create user stories for chat feature
@Mike will update architecture doc

格式2：姓名+动作动词

Sarah to create user stories
Mike will update architecture doc
Lisa should review the mockups

格式3：Action: 姓名 - 任务

Action: Sarah - create user stories
Action Item: Mike - update architecture

格式4：TODO带经办人

TODO: Create user stories (Sarah)
TODO: Update docs - Mike

格式5：带姓名的项目符号

- Sarah: create user stories
- Mike - update architecture

Extraction Logic

提取逻辑

For each action item, extract:

Assignee Name
- Text after @ symbol
- Name before "to", "will", "should"
- Name after "Action:" or in parentheses
- First/last name or full name
Task Description
- Text after "to", "will", "should", "-", ":"
- Remove markers (@, Action:, TODO:)
- Keep original wording
- Include enough context
Context (optional but helpful)
- Meeting title/date if available
- Surrounding discussion context
- Related decisions

针对每个行动项，提取以下信息：

经办人姓名
- @符号后的文本
- “to”、“will”、“should”之前的姓名
- “Action:”之后或括号内的姓名
- 名、姓或全名
任务描述
- “to”、“will”、“should”、“-”、“:”之后的文本
- 移除标记符（@、Action:、TODO:）
- 保留原始表述
- 包含足够上下文
上下文（可选但建议包含）
- 会议标题/日期（如有）
- 相关讨论内容
- 已做出的决策

Example Parsing

解析示例

Input:

undefined

输入：

undefined

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:**

Assignee: Sarah Task: Create user stories for chat feature Context: Product Planning meeting - Dec 3
Assignee: Mike Task: Update the architecture doc Context: Product Planning meeting - Dec 3
Assignee: Lisa Task: Review and approve design mockups Context: Product Planning meeting - Dec 3

---

Action Items:

@Sarah to create user stories for chat feature
Mike will update the architecture doc
Lisa: review and approve design mockups


**解析结果：**

经办人: Sarah 任务: Create user stories for chat feature 上下文: Product Planning meeting - Dec 3
经办人: Mike 任务: Update the architecture doc 上下文: Product Planning meeting - Dec 3
经办人: Lisa 任务: Review and approve design mockups 上下文: Product Planning meeting - Dec 3

---

Step 3: Ask for Project Key

步骤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)"

在查询用户或创建任务之前，确定Jira项目。

询问：“我应该在哪个Jira项目中创建这些任务？（例如：PROJ、PRODUCT、ENG）”

If User is Unsure

若用户不确定

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)"

调用

getVisibleJiraProjects

展示可选项目：

getVisibleJiraProjects(
  cloudId="...",
  action="create"
)

展示内容：“我找到了你可以创建任务的项目：PROJ（Project Alpha）、PRODUCT（Product Team）、ENG（Engineering）”

Step 4: Lookup Account IDs

步骤4：查询账号ID

For each assignee name, find their Jira account ID.

针对每个经办人姓名，查找其Jira账号ID。

Lookup Process

查询流程

lookupJiraAccountId(
  cloudId="...",
  searchString="[assignee name]"
)

The search string can be:

Full name: "Sarah Johnson"
First name: "Sarah"
Last name: "Johnson"
Email: "sarah@company.com"

lookupJiraAccountId(
  cloudId="...",
  searchString="[经办人姓名]"
)

搜索字符串可以是：

全名：“Sarah Johnson”
名：“Sarah”
姓：“Johnson”
邮箱：“sarah@company.com”

Handle Results

处理查询结果

Scenario A: Exact Match (1 result)

✅ Found: Sarah Johnson (sarah.johnson@company.com)
→ 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 (sarah.johnson@company.com)
2. Sarah Smith (sarah.smith@company.com)

Which user should be assigned the task "Create user stories"?

场景A：精确匹配（1个结果）

✅ 找到：Sarah Johnson (sarah.johnson@company.com)
→ 使用结果中的accountId

场景B：无匹配结果（0个结果）

⚠️ 在Jira中未找到用户“Sarah”。

选项：
1. 创建未分配的任务（后续手动分配）
2. 跳过该任务
3. 尝试不同的姓名格式（例如：“Sarah Johnson”）

你希望选择哪种方式？

场景C：多个匹配结果（2个及以上）

⚠️ 找到多个名为“Sarah”的用户：
1. Sarah Johnson (sarah.johnson@company.com)
2. Sarah Smith (sarah.smith@company.com)

任务“Create user stories”应该分配给哪位用户？

Best Practices

最佳实践

Try full name first ("Sarah Johnson")
If no match, try first name only ("Sarah")
If still no match, ask user
Cache results (don't lookup same person twice)

优先尝试全名（“Sarah Johnson”）
若无匹配，仅尝试名（“Sarah”）
若仍无匹配，询问用户
缓存查询结果（同一人无需重复查询）

Step 5: Present Action Items

步骤5：展示行动项

CRITICAL: Always show the parsed action items to the user BEFORE creating any tasks.

关键： 在创建任何任务之前，务必先向用户展示解析后的行动项。

Presentation Format

展示格式

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

我从会议记录中找到了[N]个行动项。是否要在[PROJECT]项目中创建这些Jira任务？

1. [TASK] [任务描述]
   经办人: [姓名]（[邮箱，若找到]）
   上下文: [会议标题/日期]

2. [TASK] [任务描述]
   经办人: [姓名]（[邮箱，若找到]）
   上下文: [会议标题/日期]

[...所有任务依次列出...]

你希望我：
1. 创建所有任务
2. 跳过部分任务（请指明哪些？）
3. 修改任务描述或经办人

Wait for Confirmation

等待确认

Do NOT create tasks until user confirms. Options:

"Yes, create all" → proceed
"Skip task 3" → create all except #3
"Change assignee for task 2" → ask for new assignee
"Edit description" → ask for changes

在用户确认之前，请勿创建任务。可选操作：

“是的，创建所有任务” → 继续执行
“跳过任务3” → 创建除#3之外的所有任务
“修改任务2的经办人” → 询问新的经办人
“编辑任务描述” → 询问修改内容

Step 6: Create Tasks

步骤6：创建任务

Once confirmed, create each Jira task.

获得确认后，创建每个Jira任务。

Determine Issue Type

确定问题类型

Before creating tasks, check what issue types are available in the project:

getJiraProjectIssueTypesMetadata(
  cloudId="...",
  projectIdOrKey="PROJ"
)

Choose the appropriate issue type:

Use "Task" if available (most common)
Use "Story" for user-facing features
Use "Bug" if it's a defect
If "Task" doesn't exist, use the first available issue type or ask the user

在创建任务之前，检查项目中可用的问题类型：

getJiraProjectIssueTypesMetadata(
  cloudId="...",
  projectIdOrKey="PROJ"
)

选择合适的问题类型：

若有“Task”则使用（最常见）
用户可见的功能使用“Story”
缺陷使用“Bug”
若没有“Task”，使用第一个可用的问题类型或询问用户

For Each Action Item

针对每个行动项

createJiraIssue(
  cloudId="...",
  projectKey="PROJ",
  issueTypeName="[Task or available type]",
  summary="[Task description]",
  description="[Full description with context]",
  assignee_account_id="[looked up account ID]"
)

createJiraIssue(
  cloudId="...",
  projectKey="PROJ",
  issueTypeName="[Task或可用类型]",
  summary="[任务描述]",
  description="[包含上下文的完整描述]",
  assignee_account_id="[查询到的账号ID]"
)

Task Summary Format

任务摘要格式

Use action verbs and be specific:

✅ "Create user stories for chat feature"
✅ "Update architecture documentation"
✅ "Review and approve design mockups"
❌ "Do the thing" (too vague)

使用动作动词并保持具体：

✅ "Create user stories for chat feature"
✅ "Update architecture documentation"
✅ "Review and approve design mockups"
❌ "Do the thing"（过于模糊）

Task Description Format

任务描述格式

markdown

**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:

markdown

**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

markdown

**来自会议记录的行动项**

**任务：** [原始行动项文本]

**上下文：**
[会议标题/日期]
[相关讨论要点或决策]

**来源：** [Confluence会议记录链接（如有）]

**原始记录：**
> [会议记录中的精确引用]

示例：

markdown

**来自会议记录的行动项**

**任务：** Create user stories for chat feature

**上下文：**
Product Planning Meeting - December 3, 2025
Discussed Q1 roadmap priorities and new feature requirements

**来源：** https://yoursite.atlassian.net/wiki/spaces/TEAM/pages/12345

**原始记录：**
> @Sarah to create user stories for chat feature

Step 7: Provide Summary

步骤7：提供摘要

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

所有任务创建完成后，展示全面的摘要。

格式：

✅ 在[PROJECT]项目中创建了[N]个任务：

1. [PROJ-123] - [任务摘要]
   经办人: [姓名]
   https://yoursite.atlassian.net/browse/PROJ-123

2. [PROJ-124] - [任务摘要]
   经办人: [姓名]
   https://yoursite.atlassian.net/browse/PROJ-124

[...所有已创建任务依次列出...]

**来源：** [会议记录链接]

**后续步骤：**
- 在Jira中检查任务的准确性
- 添加任何额外细节或附件
- 必要时调整优先级
- 关联相关工单（如有）

Action Item Pattern Examples

行动项格式示例

Pattern 1: @Mentions (Most Explicit)

格式1：@提及（最明确）

@john to update documentation
@sarah will create the report
@mike should review PR #123

Parsed:

Assignee: john/sarah/mike
Task: update documentation / create the report / review PR #123

@john to update documentation
@sarah will create the report
@mike should review PR #123

解析结果：

经办人: john/sarah/mike
任务: update documentation / create the report / review PR #123

Pattern 2: Name + Action Verb

格式2：姓名+动作动词

John to update documentation
Sarah will create the report
Mike should review PR #123
Lisa needs to test the feature

Parsed:

Assignee: name before action verb
Task: text after "to/will/should/needs to"

John to update documentation
Sarah will create the report
Mike should review PR #123
Lisa needs to test the feature

解析结果：

经办人: 动作动词之前的姓名
任务: “to/will/should/needs to”之后的文本

Pattern 3: Structured Action Format

格式3：结构化行动格式

Action: John - update documentation
Action Item: Sarah - create the report
AI: Mike - review PR #123

Parsed:

Assignee: name after "Action:" and before "-"
Task: text after "-"

Action: John - update documentation
Action Item: Sarah - create the report
AI: Mike - review PR #123

解析结果：

经办人: “Action:”之后、“-”之前的姓名
任务: “-”之后的文本

Pattern 4: TODO Format

格式4：TODO格式

TODO: Update documentation (John)
TODO: Create report - Sarah
[ ] Mike: review PR #123

Parsed:

Assignee: name in parentheses or after ":"
Task: text between TODO and assignee

TODO: Update documentation (John)
TODO: Create report - Sarah
[ ] Mike: review PR #123

解析结果：

经办人: 括号内或“:”之后的姓名
任务: TODO和经办人之间的文本

Pattern 5: Bullet Lists

格式5：项目符号列表

- John: update documentation
- Sarah - create the report
* Mike will review PR #123

Parsed:

Assignee: name before ":" or "-" or action verb
Task: remaining text

- John: update documentation
- Sarah - create the report
* Mike will review PR #123

解析结果：

经办人: “:”、“-”或动作动词之前的姓名
任务: 剩余文本

Handling Edge Cases

边缘情况处理

No Action Items Found

未找到行动项

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?

如果未检测到带有经办人的行动项：

我分析了会议记录，但未找到带有明确经办人的行动项。

行动项通常遵循以下格式：
- @姓名 to do X
- 姓名 will do X
- Action: 姓名 - do X
- TODO: X (姓名)

选项：
1. 我可以搜索无经办人的TODO项
2. 你可以指出需要创建任务的具体行动项
3. 我可以为你指定的项目符号创建任务

你希望我怎么做？

Mixed Formats

混合格式

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?

如果部分行动项有经办人，部分没有：

我找到了[N]个行动项：
- [X]个带有明确经办人
- [Y]个无经办人

我应该：
1. 创建所有[N]个任务（[X]个已分配，[Y]个未分配）
2. 仅创建[X]个带有经办人的任务
3. 请你为[Y]个无经办人的任务分配经办人

你希望选择哪种方式？

Assignee Name Variations

经办人姓名变体

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?

如果同一人被以不同方式提及：

记录中提及：@sarah、Sarah、Sarah J.

这些可能指的是同一个人。我将只查询一次“Sarah”的账号ID，并将其用于所有三个提及。是否正确？

Duplicate Action Items

重复行动项

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?

如果同一任务多次出现：

我发现似乎有两个相同的行动项：
1. "@Sarah to create user stories"（第15行）
2. "Action: Sarah - create user stories"（第42行）

我应该：
1. 创建一个任务（合并重复项）
2. 创建两个独立任务
3. 跳过重复项

你希望我怎么做？

Long Task Descriptions

长任务描述

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?

如果行动项文本过长（超过200字符）：

任务“[长文本...]”非常详细。

我应该：
1. 将第一句作为摘要，剩余内容放在描述中
2. 使用完整文本作为摘要
3. 请你编辑使其更简洁

你希望选择哪种方式？

Tips for High-Quality Results

获得高质量结果的技巧

Do:

建议做法：

✅ 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

✅ 在记录中使用统一的@提及格式
✅ 尽可能包含全名
✅ 行动项描述要具体
✅ 添加上下文（原因/内容/时间）
✅ 确认前先检查解析后的任务

Don't:

避免做法：

❌ 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

❌ 在一个项目符号中为同一人混合多个任务
❌ 使用模糊的姓名（如果有5个John，不要只写“John”）
❌ 省略动作动词（不清楚要做什么）
❌ 忘记指定项目

Best Meeting Notes Format

最佳会议记录格式

undefined

undefined

Meeting Title - Date

会议标题 - 日期

Attendees: [Names]

参会者：[姓名]

Decisions

决策

[What was decided]

[做出的决策]

Action Items

行动项

@FullName to [specific task with context]
@AnotherPerson will [specific task with context]
etc.

---

@全名 to [包含上下文的具体任务]
@另一人 will [包含上下文的具体任务]
等等

---

When NOT to Use This Skill

不适用场景

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.

该技能仅用于将会议行动项转换为Jira任务。

请勿用于： ❌ 会议总结（不创建任务）
❌ 查找会议记录（使用搜索技能）
❌ 创建日历事件
❌ 通过邮件发送会议记录
❌ 通用笔记记录

仅在以下场景使用： 存在会议记录，且需要将其中的行动项转换为Jira任务。

Examples

示例

Example 1: Simple @Mentions

示例1：简单@提及

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:

Parse → 3 action items found
Project → "PROJ"
Lookup → Sarah (123), Mike (456), Lisa (789)
Present → User confirms
Create → PROJ-100, PROJ-101, PROJ-102

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

输入：

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

流程：

解析 → 找到3个行动项
项目 → "PROJ"
查询 → Sarah(123)、Mike(456)、Lisa(789)
展示 → 用户确认
创建 → PROJ-100、PROJ-101、PROJ-102

输出：

✅ 在PROJ项目中创建了3个任务：

1. PROJ-100 - Create user stories for chat feature
   经办人: Sarah Johnson
   
2. PROJ-101 - Update the architecture doc
   经办人: Mike Chen
   
3. PROJ-102 - Review design mockups
   经办人: Lisa Park

Example 2: Mixed Formats

示例2：混合格式

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:

Parse → Found 4 items (3 with assignees, 1 without)
Ask → "Found 3 with assignees, 1 without. Create all or only assigned?"
User → "All, make the last one unassigned"
Create → 4 tasks (3 assigned, 1 unassigned)

输入：

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

流程：

解析 → 找到4个项（3个有经办人，1个无）
询问 → "找到3个有经办人的项，1个无。是否创建所有任务还是仅创建有经办人的？"
用户 → "全部创建，最后一个设为未分配"
创建 → 4个任务（3个已分配，1个未分配）

Example 3: Name Lookup Issue

示例3：姓名查询问题

Input:

Sprint Planning

Action Items:
- @John to update tests
- @Sarah to refactor code

Process:

Parse → 2 action items
Lookup "John" → Found 3 Johns!
Ask → "Which John? (John Smith, John Doe, John Wilson)"
User → "John Smith"
Create → Both tasks assigned correctly

输入：

Sprint Planning

Action Items:
- @John to update tests
- @Sarah to refactor code

流程：

解析 → 2个行动项
查询“John” → 找到3个John！
询问 → "是哪位John？(John Smith、John Doe、John Wilson)"
用户 → "John Smith"
创建 → 两个任务均正确分配

Quick Reference

快速参考

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 X
```
```
Name to/will/should X
```
```
Action: Name - X
```
```
TODO: X (Name)
```
```
Name: X
```

Always:

Present parsed tasks before creating
Handle name lookup failures gracefully
Include context in task descriptions
Provide summary with links

Remember:

Human-in-loop is critical (show before creating)
Name lookup can fail (have fallback)
Be flexible with pattern matching
Context preservation is important

主要工具：

getConfluencePage

（如果提供URL）或使用粘贴的文本
账号查询：

lookupJiraAccountId(searchString)

任务创建：

createJiraIssue

并传入

assignee_account_id

需要识别的行动项格式：

```
@Name to/will/should X
```
```
Name to/will/should X
```
```
Action: Name - X
```
```
TODO: X (Name)
```
```
Name: X
```

务必：

创建前展示解析后的任务
优雅处理姓名查询失败的情况
在任务描述中包含上下文
提供带有链接的摘要

记住：

人工参与至关重要（创建前展示）
姓名查询可能失败（要有备选方案）
模式匹配要灵活
上下文保留很重要