tapd-story-tasks-analysis
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseTAPD 需求任务分析
TAPD Requirement Task Analysis
分析指定 TAPD 需求下的任务情况。
Analyze the task status under the specified TAPD requirement.
使用场景
Usage Scenarios
- 用户要求分析某个需求的任务排期
- 用户想判断需求推进是否正常
- 用户希望从任务角度识别延期风险、负责人分布或测试缺口
- Users request to analyze task scheduling for a specific requirement
- Users want to determine if the requirement progress is normal
- Users hope to identify delay risks, responsible person distribution, or testing gaps from the task perspective
执行步骤
Execution Steps
- 先确认分析对象:
- 用户直接给了 ,直接使用
story_id - 用户给的是本地 Markdown 文件,先读取 frontmatter 中的
tapd_id
- 用户直接给了
- 执行:
bash
tapd story get <story-id>
tapd story tasks <story-id> --all- 读取:
references/analysis-output.md
- 按规范输出:
- 分析对象
- 总览
- 关键汇总
- 风险与问题
- 建议动作
- 明细
- First confirm the analysis target:
- If the user directly provides a , use it directly
story_id - If the user provides a local Markdown file, first read the from the frontmatter
tapd_id
- If the user directly provides a
- Execute:
bash
tapd story get <story-id>
tapd story tasks <story-id> --all- Read:
references/analysis-output.md
- Output in accordance with specifications:
- Analysis target
- Overview
- Key summary
- Risks and issues
- Recommended actions
- Details
分析重点
Analysis Focus
- 进行中任务是否过少,导致整体推进偏慢
- 未开始任务是否大量堆积在后段排期
- 测试任务是否明显晚于开发任务
- 是否存在负责人过于集中或无人负责的情况
- 工时、时间窗口、任务状态是否匹配
- Whether there are too few in-progress tasks, leading to slow overall progress
- Whether a large number of unstarted tasks are piled up in the later scheduling period
- Whether testing tasks are significantly later than development tasks
- Whether there is a situation where responsible persons are overly concentrated or no one is in charge
- Whether man-hours, time windows, and task status match
注意事项
Notes
- 不要直接复制原始命令输出
- 明细默认按 分组
进行中 / 未开始 / 已完成 - 如果任务数量很多,只保留关键任务和异常任务
- Do not directly copy the original command output
- Details are grouped by by default
In Progress / Not Started / Completed - If there are a large number of tasks, only keep key tasks and abnormal tasks