tasks-generator

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Tasks Generator

任务生成器

Transform PRD documents into structured, sprint-based development tasks with dependency analysis.

将PRD文档转换为结构化、基于迭代的开发任务，并进行依赖分析。

Input

输入

Preferred: PRD file path provided in

$ARGUMENTS

Auto-pick mode (if

$ARGUMENTS

is empty):

Reuse the most recent project folder/path from this chat/session.
If unavailable, use env var
```
IDEAS_ROOT
```
when present.
Else check shared marker file
```
~/.config/ideas-root.txt
```
.
Backward compatibility fallback:
```
~/.openclaw/ideas-root.txt
```
.
If still unavailable, auto-discover the newest folder containing
```
prd.md
```
under:
- ```
/home/luongnv/workspace/ideas
```
  (default)
- ```
/home/luongnv/workspace/idea-2-prd
```
  (legacy fallback)
Use
```
<project>/prd.md
```
.
If multiple candidates are plausible, ask user to choose.

首选方式：在

$ARGUMENTS

中提供PRD文件路径。

自动选择模式（当

$ARGUMENTS

为空时）：

重用本次对话/会话中最近使用的项目文件夹/路径。
如果不可用，使用环境变量
```
IDEAS_ROOT
```
（若存在）。
否则检查共享标记文件
```
~/.config/ideas-root.txt
```
。
向后兼容备选：
```
~/.openclaw/ideas-root.txt
```
。
如果仍不可用，自动发现包含
```
prd.md
```
的最新文件夹，搜索路径包括：
- ```
/home/luongnv/workspace/ideas
```
  （默认路径）
- ```
/home/luongnv/workspace/idea-2-prd
```
  （旧版备选路径）
使用
```
<project>/prd.md
```
。
如果存在多个合理候选路径，请让用户选择。

Pre-checks

预检查

Resolve
```
PRD_PATH
```
(from
```
$ARGUMENTS
```
or auto-pick mode) and verify it exists
Check for existing
```
tasks.md
```
in the same directory - create backup if exists:
```
tasks_backup_YYYY_MM_DD_HHMMSS.md
```
Look for supporting docs in same directory:
```
tad.md
```
,
```
ux_design.md
```
,
```
brand_kit.md
```

解析
```
PRD_PATH
```
（来自
```
$ARGUMENTS
```
或自动选择模式）并验证文件是否存在
检查同一目录下是否存在现有
```
tasks.md
```
文件 - 若存在则创建备份：
```
tasks_backup_YYYY_MM_DD_HHMMSS.md
```
查找同一目录下的支持文档：
```
tad.md
```
、
```
ux_design.md
```
、
```
brand_kit.md
```

Workflow

工作流程

Phase 1: Extract Requirements

阶段1：提取需求

From PRD, extract:

Core features and value proposition
User stories and personas
Functional requirements
Non-functional requirements (performance, security)
Technical constraints and dependencies

从PRD中提取：

核心功能与价值主张
用户故事与用户角色
功能需求
非功能需求（性能、安全性）
技术约束与依赖关系

Phase 2: Define Development Phases

阶段2：定义开发阶段

POC (Proof of Concept):

Single most important feature proving core value
Minimal implementation, 1-2 sprints

MVP (Minimum Viable Product):

Essential features for first release
Core user workflows

Full Features:

Remaining enhancements
Nice-to-haves and polish

POC（概念验证）：

单个最重要的、能证明核心价值的功能
最小化实现，1-2个迭代

MVP（最小可行产品）：

首次发布所需的核心功能
核心用户工作流

完整功能：

剩余的增强功能
锦上添花的功能与优化

Phase 3: Create Sprint Plan

阶段3：创建迭代计划

Sprint	Focus	Scope
Sprint 1	POC	Core differentiating feature
Sprint 2	MVP Foundation	Auth, data models, primary workflows
Sprint 3	MVP Completion	UI/UX, integration, validation
Sprint 4+	Full Features	Enhancements, optimization, polish

迭代	重点	范围
Sprint 1	POC	核心差异化功能
Sprint 2	MVP基础	认证、数据模型、主要工作流
Sprint 3	MVP完成	UI/UX、集成、验证
Sprint 4+	完整功能	增强、优化、打磨

Phase 4: Analyze Dependencies

阶段4：依赖分析

Map Dependencies: For each task, identify "Depends On" and "Blocks"
Group Parallel Tasks: Assign tasks to execution waves
Calculate Critical Path: Longest dependency chain = minimum duration
Validate: Check for circular dependencies, broken references

映射依赖关系：为每个任务识别“依赖于”和“阻塞项”
分组并行任务：将任务分配到执行批次
计算关键路径：最长的依赖链 = 最短耗时
验证：检查是否存在循环依赖、无效引用

Phase 5: Generate tasks.md

阶段5：生成tasks.md

Create

tasks.md

in same directory as PRD. See references/tasks-template.md for full template.

在PRD所在的同一目录下创建

tasks.md

。完整模板请参考references/tasks-template.md。

Task Format

任务格式

Each task must include:

markdown

undefined

每个任务必须包含：

markdown

undefined

Task X.Y: [Action-oriented Title]

Task X.Y: [面向动作的标题]

Description: What and why, referencing PRD

Acceptance Criteria:

Specific, testable condition 1
Specific, testable condition 2

Dependencies: None / Task X.X

PRD Reference: [Section]

undefined

描述：任务内容与目的，需关联PRD

验收标准：

具体、可测试的条件1
具体、可测试的条件2

依赖关系：无 / Task X.X

PRD参考：[章节]

undefined

Task Guidelines

任务指南

Title: Action-oriented (e.g., "Implement user authentication API")
Size: 1-3 days of work; break larger features
Criteria: Cover happy path and edge cases
Dependencies: List prerequisites and external dependencies

标题：面向动作（例如：“实现用户认证API”）
规模：1-3天的工作量；若功能较大则拆分
验收标准：覆盖正常流程与边缘情况
依赖关系：列出前置条件与外部依赖

Quality Checks

质量检查

README Maintenance (ideas repo)

README维护（ideas仓库）

After writing

tasks.md

, if the PRD lives inside an

ideas

repo, update the repo README ideas table:

Preferred:
```
cd
```
to the repo root and run
```
python3 scripts/update_readme_ideas_index.py
```
(if it exists)
Fallback: update
```
README.md
```
manually (ensure Tasks status becomes ✅ for that idea)

生成

tasks.md

后，如果PRD位于

ideas

仓库内，更新仓库README中的创意表格：

首选方式：切换到仓库根目录并运行
```
python3 scripts/update_readme_ideas_index.py
```
（若该脚本存在）
备选方式：手动更新
```
README.md
```
（确保该创意的Tasks状态变为✅）

Reporting with GitHub links (mandatory)

含GitHub链接的报告（必填）

When reporting completion, include:

GitHub link to
```
tasks.md
```
GitHub link to
```
README.md
```
when it was updated
Commit hash

Link format:

https://github.com/luongnv89/ideas/blob/main/<relative-path>

完成后报告需包含：

```
tasks.md
```
的GitHub链接
若更新了
```
README.md
```
，需提供其GitHub链接
提交哈希值

链接格式：

https://github.com/luongnv89/ideas/blob/main/<relative-path>

Output Summary

输出摘要

After generating, provide:

File location
Sprint overview (count, tasks per sprint)
MVP scope summary
Dependency analysis (waves, critical path, bottlenecks)
Flagged ambiguous requirements
Next steps: Review Sprint 1 and Wave 1 tasks first

生成完成后需提供：

文件位置
迭代概览（数量、每个迭代的任务数）
MVP范围摘要
依赖分析（批次、关键路径、瓶颈）
已标记的模糊需求
下一步：优先审查Sprint 1和Wave 1的任务