action-item-organizer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Action Item Organizer

可执行任务整理框架

This skill provides a systematic framework for extracting actionable items from unstructured documents and transforming them into well-organized, prioritized, trackable checklists in markdown format.

本技能提供一套系统化框架，可从非结构化文档中提取可执行任务，并将其转换为格式规范、优先级明确、可追踪的markdown格式清单。

When to Use This Skill

适用场景

Converting code review reports into TODO lists
Extracting action items from meeting notes
Organizing audit findings into remediation checklists
Breaking down project planning documents into task lists
Structuring issue reports into actionable work items
Creating trackable checklists from any document containing embedded action items
Organizing team backlogs by priority
Creating sprint planning checklists

将代码审查报告转换为TODO列表
从会议纪要中提取可执行任务
将审计结果整理为整改清单
将项目规划文档拆解为任务列表
将问题报告结构化为可执行工作项
从任何包含内嵌可执行任务的文档创建可追踪清单
按优先级整理团队待办事项
创建Sprint规划清单

Core Principles

核心原则

1. Extraction with Context Preservation

1. 保留上下文的提取

Action items must be extracted with sufficient context so that anyone reading the checklist understands:

What needs to be done
Why it matters
Where it applies (files, systems, components)
Who is responsible
When it should be completed (priority and estimates)

提取可执行任务时必须保留足够的上下文，以便任何查看清单的人都能理解：

要做什么
为什么重要
适用范围（文件、系统、组件）
负责人
完成时间要求（优先级和预估时长）

2. Priority-Based Organization

2. 基于优先级的组织

Use a clear priority framework to organize items by urgency and impact:

P0 / Blockers: Critical issues that prevent progress, deployment, or merge
P1 / High Priority: Significant quality, security, or correctness concerns requiring prompt attention
P2 / Medium Priority: Important improvements and refactorings that enhance the system
P3 / Low Priority: Future optimizations, minor suggestions, and nice-to-have enhancements

Within each priority level, group related items logically (e.g., security items together, performance items together).

使用清晰的优先级框架，按紧急程度和影响范围整理任务：

P0 / 阻塞项：阻碍进度、部署或合并的关键问题
P1 / 高优先级：涉及质量、安全或正确性的重大问题，需立即处理
P2 / 中优先级：提升系统性能的重要改进和重构任务
P3 / 低优先级：未来优化、次要建议和锦上添花的增强功能

在同一优先级内，按逻辑分组相关任务（例如，将安全相关任务放在一起，性能相关任务放在一起）。

3. Nested Structure for Complex Tasks

3. 复杂任务的嵌套结构

Break down complex action items into hierarchical checklists:

Parent items represent the main task or goal
Child items represent specific steps or sub-tasks
Grandchild items represent detailed implementation steps

This creates a clear execution path and allows for granular progress tracking.

将复杂的可执行任务拆解为层级化清单：

父项代表主要任务或目标
子项代表具体步骤或子任务
孙项代表详细的实施步骤

这将创建清晰的执行路径，并支持精细化的进度追踪。

4. Traceability and Metadata

4. 可追溯性与元数据

Maintain links between action items and their sources:

File paths and line numbers
Issue or tracking IDs
Owner or responsible team
Time estimates
Original context from source document

This enables bidirectional traceability and informed prioritization.

保持可执行任务与来源文档的关联：

文件路径和行号
问题或追踪ID
负责人或负责团队
时间预估
来源文档的原始上下文

这支持双向追溯，并为优先级划分提供依据。

Extraction Workflow

提取工作流

Step 1: Document Analysis

步骤1：文档分析

Read the complete source document
Identify sections containing actionable content:
- "Action Items", "Todo List", "Recommendations"
- "Issues", "Findings", "Follow-ups"
- "Next Steps", "Tasks", "Requirements"
Understand the document structure and conventions

完整阅读来源文档
识别包含可执行内容的章节：
- "Action Items"、"Todo List"、"Recommendations"
- "Issues"、"Findings"、"Follow-ups"
- "Next Steps"、"Tasks"、"Requirements"
理解文档结构和约定

Step 2: Action Item Identification

步骤2：可执行任务识别

Extract items that are:

Actionable: Specific tasks that can be completed
Testable: Clear completion criteria
Assigned or assignable: Can be owned by a person or team
Contextual: Include enough detail to understand the task

Skip items that are:

Purely informational (unless they imply action)
Already completed
Vague or unclear without additional context

提取符合以下特征的任务：

可执行：可完成的具体任务
可测试：有明确的完成标准
可指派：可分配给个人或团队
有上下文：包含足够的任务细节

跳过以下内容：

纯信息性内容（除非隐含行动要求）
已完成的任务
模糊或缺乏足够上下文的内容

Step 3: Metadata Extraction

步骤3：元数据提取

For each action item, extract:

Required Metadata:

Task description
Priority level

Optional Metadata (extract if available):

File paths and line numbers
Owner/responsible party
Time estimate
Issue/tracking numbers
Category or domain (security, performance, etc.)
Implementation steps or sub-tasks

为每个可执行任务提取以下信息：

必填元数据：

任务描述
优先级级别

可选元数据（如有则提取）：

文件路径和行号
负责人/责任方
时间预估
问题/追踪编号
类别或领域（安全、性能等）
实施步骤或子任务

Step 4: Priority Classification

步骤4：优先级分类

Assign each item to a priority level based on:

P0 Criteria:

Blocks deployment or merge
Critical security vulnerability
Data loss or corruption risk
System availability impact
Compliance violation

P1 Criteria:

Significant security concern
Major performance impact
Correctness issues affecting functionality
Important architectural problems
High technical debt

P2 Criteria:

Code quality improvements
Moderate refactoring needs
Test coverage gaps
Documentation needs
Minor performance optimizations

P3 Criteria:

Code style and consistency
Future enhancements
Nice-to-have features
Minor optimizations
Exploratory tasks

根据以下标准为每个任务分配优先级：

P0 判定标准：

阻碍部署或合并
严重安全漏洞
数据丢失或损坏风险
影响系统可用性
违反合规要求

P1 判定标准：

重大安全问题
严重性能影响
影响功能正确性的问题
重要架构缺陷
高额技术债务

P2 判定标准：

代码质量改进
中度重构需求
测试覆盖率缺口
文档需求
次要性能优化

P3 判定标准：

代码风格与一致性
未来增强功能
锦上添花的特性
次要优化
探索性任务

Step 5: Hierarchical Organization

步骤5：层级化组织

Structure items using nested checklists:

markdown

- [ ] **Category: Main task description** (#tracking-id)
  - [ ] Sub-task 1
  - [ ] Sub-task 2
    - [ ] Detailed implementation step
  - **File**: `path/to/file.ext:lines`
  - **Owner**: Team/Person
  - **Estimate**: Time estimate
  - **Context**: Why this matters and what it achieves

使用嵌套清单结构整理任务：

markdown

- [ ] **类别：主要任务描述** (#追踪ID)
  - [ ] 子任务1
  - [ ] 子任务2
    - [ ] 详细实施步骤
  - **文件**：`path/to/file.ext:lines`
  - **负责人**：团队/个人
  - **预估时长**：时间预估
  - **上下文**：任务的重要性和目标

Step 6: Summary Generation

步骤6：摘要生成

For each priority section, calculate:

Total number of items
Total estimated hours (if available)
Completion percentage (if tracking existing checklist)

为每个优先级章节计算：

任务总数
总预估时长（如有）
完成百分比（如果追踪现有清单）

Step 7: Output Formatting

步骤7：输出格式化

Create a structured markdown document with:

Header: Title, generation metadata, source reference
Overview: Total items and time across all priorities
Priority Sections: P0, P1, P2, P3 with summaries
Completion Tracking: Progress metrics at the bottom

创建结构化的markdown文档，包含：

标题：标题、生成元数据、来源参考
概述：所有优先级的任务总数和总时长
优先级章节：P0、P1、P2、P3及对应摘要
进度追踪：底部的进度指标

Checklist Format Standards

清单格式标准

Basic Checkbox Item

基础复选框项

markdown

- [ ] Task description

markdown

- [ ] 任务描述

Item with Metadata

带元数据的任务项

markdown

- [ ] **Category: Task description** (#123)
  - **File**: `src/file.js:45-67`
  - **Owner**: Backend Team
  - **Estimate**: 3 hours
  - **Context**: Explanation of why this matters

markdown

- [ ] **类别：任务描述** (#123)
  - **文件**：`src/file.js:45-67`
  - **负责人**：后端团队
  - **预估时长**：3小时
  - **上下文**：任务重要性说明

Nested Sub-tasks

嵌套子任务

markdown

- [ ] **Security: Implement authentication** (#456)
  - [ ] Add session validation
  - [ ] Implement rate limiting
  - [ ] Add authorization checks
  - **File**: `api/auth.ts`
  - **Owner**: Security Team
  - **Estimate**: 8 hours

markdown

- [ ] **安全：实现身份验证** (#456)
  - [ ] 添加会话验证
  - [ ] 实现速率限制
  - [ ] 添加授权检查
  - **文件**：`api/auth.ts`
  - **负责人**：安全团队
  - **预估时长**：8小时

Section Summary

章节摘要

markdown

undefined

markdown

undefined

P0 - Blockers (Must Fix Before Merge)

P0 - 阻塞项（合并前必须修复）

Summary: 5 items | 12 hours estimated

Item 1...
Item 2...

undefined

摘要：5项 | 预估12小时

任务1...
任务2...

undefined

Complete Output Template

完整输出模板

markdown

undefined

markdown

undefined

TODO List

Generated from: [source-document.md] Date: YYYY-MM-DD HH:MM:SS Total Items: X | Total Estimated Hours: Y

生成自：[source-document.md] 日期：YYYY-MM-DD HH:MM:SS 总任务数：X | 总预估时长：Y

P0 - Blockers (Must Fix Before Merge)

P0 - 阻塞项（合并前必须修复）

Summary: N items | M hours estimated

Category: Task description (#id)
- Sub-task
- File:
```
path/file.ext:lines
```
- Owner: Team
- Estimate: X hours
- Context: Why this matters

摘要：N项 | 预估M小时

类别：任务描述 (#id)
- 子任务
- 文件：
```
path/file.ext:lines
```
- 负责人：团队
- 预估时长：X小时
- 上下文：任务重要性说明

P1 - High Priority

P1 - 高优先级

Summary: N items | M hours estimated

[items...]

摘要：N项 | 预估M小时

[任务列表...]

P2 - Medium Priority

P2 - 中优先级

Summary: N items | M hours estimated

[items...]

摘要：N项 | 预估M小时

[任务列表...]

P3 - Low Priority / Future

P3 - 低优先级 / 未来任务

Summary: N items | M hours estimated

[items...]

摘要：N项 | 预估M小时

[任务列表...]

Completion Tracking

进度追踪

P0 Blockers: 0/N completed (0%)
P1 High Priority: 0/M completed (0%)
P2 Medium Priority: 0/K completed (0%)
P3 Low Priority: 0/J completed (0%)

Overall Progress: 0/X tasks completed (0%)

undefined

P0 阻塞项：0/N 已完成 (0%)
P1 高优先级：0/M 已完成 (0%)
P2 中优先级：0/K 已完成 (0%)
P3 低优先级：0/J 已完成 (0%)

整体进度：0/X 任务已完成 (0%)

undefined

Best Practices

最佳实践

Context Preservation

上下文保留

Include enough detail that readers understand WHY each task matters
Preserve the original rationale and justification
Link to related issues or documentation
Capture the impact of not completing the task

包含足够细节，让读者理解每个任务的重要性
保留原始理由和依据
关联到相关问题或文档
记录未完成任务的影响

Logical Grouping

逻辑分组

Group related items within priority levels
Use category prefixes (Security, Performance, Testing, etc.)
Keep dependent tasks near each other
Consider execution order in grouping

在同一优先级内分组相关任务
使用类别前缀（安全、性能、测试等）
将依赖任务放在一起
分组时考虑执行顺序

Actionability

可执行性

Each checkbox should be a clear, completable action
Avoid vague tasks like "improve performance"
Use specific verbs: implement, add, remove, refactor, fix
Include success criteria when helpful

每个复选框对应一个清晰、可完成的动作
避免模糊任务，如“提升性能”
使用具体动词：实现、添加、移除、重构、修复
必要时包含成功标准

Traceability

可追溯性

Always link back to source files and line numbers
Include issue or tracking IDs
Reference original documentation
Enable bidirectional navigation

始终关联到源文件和行号
包含问题或追踪ID
参考原始文档
支持双向导航

Completeness

完整性

Verify all action items from source are included
Preserve nested relationships
Don't lose metadata in extraction
Handle edge cases explicitly

验证来源文档中的所有可执行任务都已包含
保留嵌套关系
提取过程中不丢失元数据
明确处理边缘情况

Handling Edge Cases

边缘情况处理

Missing Priority

缺失优先级

Place in "Uncategorized" section at bottom
Flag for review and prioritization
Use context clues to infer if possible

放在底部的“未分类”章节
标记为需要审核和优先级划分
如有可能，通过上下文线索推断优先级

Missing Metadata

缺失元数据

Use "TBD" markers for missing estimates
Note "File: TBD" to prompt investigation
Flag items with insufficient context

对缺失的预估时长使用“TBD”标记
标注“文件：TBD”以提示后续调查
标记上下文不足的任务

Conflicting Priorities

优先级冲突

Defer to explicit priority markers in source
Consider impact and urgency
Document rationale for priority assignment

以来源文档中的明确优先级标记为准
考虑影响范围和紧急程度
记录优先级分配的理由

Existing TODO Files

已存在的TODO文件

Confirm before overwriting
Consider timestamped filenames
Merge with existing if appropriate

覆盖前确认
考虑使用带时间戳的文件名
如有需要，与现有内容合并

Multiple Sources

多来源文档

Process each independently
Or consolidate into single list with source markers
Deduplicate when appropriate

独立处理每个来源
或合并为单个列表并标记来源
必要时去重

Anti-Patterns to Avoid

需避免的反模式

Losing Context

丢失上下文

Bad:

- [ ] Fix bug

Good:

- [ ] **Bug Fix: Handle null response in user fetch** (#789)

错误示例：

- [ ] 修复bug

正确示例：

- [ ] **Bug修复：处理用户获取接口的空响应** (#789)

Flat Structure

扁平结构

Bad: Ten separate items for one complex task Good: One parent with nested sub-tasks

错误示例：将一个复杂任务拆分为10个独立项正确示例：一个父项包含嵌套子任务

Missing Traceability

缺失可追溯性

Bad: No file paths or line numbers Good: Always include location metadata

错误示例：无文件路径或行号正确示例：始终包含位置元数据

Vague Tasks

模糊任务

Bad:

- [ ] Improve performance

Good:

- [ ] **Performance: Add caching to user query** - reduces DB calls from 100/req to 1/req

错误示例：

- [ ] 提升性能

正确示例：

- [ ] **性能优化：为用户查询添加缓存** - 将数据库调用从100次/请求减少到1次/请求

Priority Inflation

优先级膨胀

Bad: Everything is P0 Good: Reserve P0 for true blockers

错误示例：所有任务都标记为P0 正确示例：仅将真正的阻塞项标记为P0

Examples

示例

Example 1: Code Review Report to TODO

示例1：代码审查报告转TODO列表

Input: Code review report with security findings

Output:

markdown

undefined

输入：包含安全问题的代码审查报告

输出：

markdown

undefined

TODO List

Generated from: CODE_REVIEW_REPORT.md Date: 2025-12-09 10:30:00 Total Items: 8 | Total Estimated Hours: 23

生成自：CODE_REVIEW_REPORT.md 日期：2025-12-09 10:30:00 总任务数：8 | 总预估时长：23

P0 - Blockers (Must Fix Before Merge)

P0 - 阻塞项（合并前必须修复）

Summary: 2 items | 5 hours estimated

Security: Add authentication to token endpoint (#1)
- Implement getServerSession check
- Add authorization verification
- Add rate limiting (10 req/min per IP)
- File:
```
app/api/livekit/token/route.ts:15-30
```
- Owner: Backend Team
- Estimate: 4 hours
- Context: Public endpoint exposed without auth allows unauthorized access
Security: Remove hardcoded credentials (#2)
- Remove fallback values from environment reads
- Add explicit validation for required credentials
- Fail fast if credentials missing at startup
- File:
```
experiments/livekit/src/index.ts:182-183
```
- Owner: Backend Team
- Estimate: 1 hour
- Context: Hardcoded fallbacks create security risk in production

undefined

摘要：2项 | 预估5小时

安全：为token接口添加身份验证 (#1)
- 实现getServerSession校验
- 添加授权验证
- 添加速率限制（10次请求/分钟/IP）
- 文件：
```
app/api/livekit/token/route.ts:15-30
```
- 负责人：后端团队
- 预估时长：4小时
- 上下文：公开接口未做身份验证，存在未授权访问风险
安全：移除硬编码凭证 (#2)
- 从环境变量读取中移除 fallback 值
- 为必填凭证添加显式验证
- 启动时如果凭证缺失则直接失败
- 文件：
```
experiments/livekit/src/index.ts:182-183
```
- 负责人：后端团队
- 预估时长：1小时
- 上下文：硬编码的fallback值会带来生产环境安全风险

undefined

Example 2: Meeting Notes to Action Items

示例2：会议纪要转可执行任务

Input: Team meeting notes with scattered action items

Output:

markdown

undefined

输入：分散包含可执行任务的团队会议纪要

输出：

markdown

undefined

Action Items - Q4 Planning Meeting

可执行任务 - Q4规划会议

Generated from: team-meeting-2025-12-09.md Date: 2025-12-09 14:00:00 Total Items: 12 | Total Estimated Hours: 45

生成自：team-meeting-2025-12-09.md 日期：2025-12-09 14:00:00 总任务数：12 | 总预估时长：45

P1 - High Priority

P1 - 高优先级

Summary: 5 items | 20 hours estimated

Architecture: Design new API gateway (#45)
- Research existing solutions (Kong, Tyk, AWS API Gateway)
- Document requirements and constraints
- Create comparison matrix
- Present findings to team
- Owner: Sarah
- Estimate: 8 hours
- Context: Current gateway hitting scale limits at 1000 req/s
Documentation: Update onboarding guide (#46)
- Add sections on local development setup
- Document deployment process
- Add troubleshooting guide
- Owner: Mike
- Estimate: 4 hours
- Context: New engineers spending 2 days on setup

undefined

摘要：5项 | 预估20小时

架构：设计新的API网关 (#45)
- 调研现有解决方案（Kong、Tyk、AWS API Gateway）
- 记录需求和约束
- 创建对比矩阵
- 向团队展示调研结果
- 负责人：Sarah
- 预估时长：8小时
- 上下文：当前网关在1000请求/秒时达到性能瓶颈
文档：更新入职指南 (#46)
- 添加本地开发环境搭建章节
- 记录部署流程
- 添加故障排除指南
- 负责人：Mike
- 预估时长：4小时
- 上下文：新工程师需要花费2天时间完成环境搭建

undefined

Reference Files

参考文件

For detailed guidance on specific aspects of action item organization:

references/priority-framework.md
: Comprehensive priority classification criteria with domain-specific examples
references/metadata-extraction-patterns.md
: Detailed patterns for extracting different types of metadata from various document formats
references/TODO_LIST.template.md
: TODO list template with priority-based organization (P0-P3), blocked tasks, and completion tracking

Load these references when you need deeper guidance on priority decisions or metadata extraction strategies.

如需获取可执行任务整理的具体细节指导：

references/priority-framework.md
：包含领域特定示例的完整优先级分类标准
references/metadata-extraction-patterns.md
：从不同文档格式提取各类元数据的详细模式
references/TODO_LIST.template.md
：基于优先级（P0-P3）、阻塞任务和进度追踪的TODO列表模板

当你需要优先级决策或元数据提取的深度指导时，可以加载这些参考文件。