ZenTao AI Assistant (zentao-mcp-agent)

When to use this skill

当你（大语言模型）需要代替用户在禅道中查阅待办、分配任务、填报工时或操作任务状态机时，请必须启用此扩展包提供的 Tool 集合。依托我们的 MVC+RESTful 混动底层架构，你可以基于用户授权，越过繁杂的分页与项目界面，进行事项的统筹处理。

When you (a large language model) need to act on behalf of users to view to-dos, assign tasks, log work hours, or operate task state machines in ZenTao, you must enable the Tool set provided by this extension package. Relying on our MVC+RESTful hybrid underlying architecture, you can, based on user authorization, bypass complicated pagination and project interfaces to carry out overall management of matters.

💡 AI 最佳实践指引 (For LLM AI)

💡 AI Best Practice Guidelines (For LLM AI)

作为 AI Assistant，当用户提出下述意图时，请严格按照指引调用底层提供的 4 大 Tool 工具：

As an AI Assistant, when users express the following intents, please strictly follow the guidelines to call the 4 major Tools provided by the underlying layer:

1. 全视界地盘拉取 (Global Dashboard)

1. Global Dashboard Pull

触发意图：用户询问**“看看张三手头有什么活”、“最近哪些线上 Bug 延期了”**。
调用动作：调用
```
getDashboard
```
。
参数指南：通过
```
type
```
（task/bug/story）切换类型，通过
```
status
```
（doing, wait, done）过滤状态。
- ✅
```
my tasks / my bugs / my stories
```
  ：查询当前登录用户的待办，完全可用。
- ✅
```
--assign <他人>
```
  ：支持跨人员查看官方指派视角，适合主管查岗或交叉核对。
- ✅
```
manage --users <成员列表>
```
  ：管理视角聚合查询，适合主管查看单人或团队当前任务池。

Trigger Intent: Users ask "What tasks does Zhang San have on hand?", "Which online bugs have been delayed recently?".
Call Action: Call
```
getDashboard
```
.
Parameter Guide: Switch types via
```
type
```
(task/bug/story), filter status via
```
status
```
(doing, wait, done).
- ✅
```
my tasks / my bugs / my stories
```
  : Queries the to-dos of the currently logged-in user, fully available.
- ✅
```
--assign <other user>
```
  : Supports cross-user viewing of official assignment perspectives, suitable for supervisors to check work or cross-verify.
- ✅
```
manage --users <member list>
```
  : Aggregated query from a management perspective, suitable for supervisors to view the current task pool of an individual or team.

1.1 管理聚合视角补充规则 (Management Dashboard)

1.1 Supplementary Rules for Management Aggregation View

触发意图：用户说**“帮我看张三今天要盯哪些任务”、“把我们组这几个人的任务、需求、Bug 汇总出来”**。
调用动作：优先调用
```
manage
```
对应的管理聚合能力。
参数指南：
- ```
--users
```
  支持账号、中文名、多人逗号分隔。
- ```
--type
```
  支持
```
tasks/stories/bugs/all
```
  。
- 默认口径为 当前未完成项 + 当日完成/关闭项；若用户指定时间窗口，再追加
```
--date-from
```
  与
```
--date-to
```
  。
- ```
--status
```
  支持逗号分隔，如
```
doing,wait
```
  。
- ```
--deadline-from
```
  、
```
--deadline-to
```
  可用于筛选临期任务；
```
--overdue-only
```
  可用于只看已延期项。
- 管理视角中的状态是跨类型语义映射，不是简单字面匹配：例如
```
doing,wait,done
```
  会自动覆盖任务、需求、Bug 各自对应的待处理/已完成状态。
- ```
--team-name <团队名>
```
  可直接复用本地缓存的团队成员列表，适合固定小组的日常巡检。
- 输出中的“总计”会严格跟随当前
```
--type
```
  查询口径，并额外展示过滤条件，避免将定向查询误读为全量统计。
- ```
my tasks --assign <账号>
```
  与
```
manage --users <成员>
```
  不可混为一谈：前者是官方指派地盘，后者是管理汇总视角。
- 输出展示优先使用中文友好字段，方便用户直接阅读，也便于大模型后续做晨报、周报和催办摘要。

Trigger Intent: Users say "Help me check which tasks Zhang San needs to oversee today", "Summarize the tasks, requirements, and bugs of our team members".
Call Action: Prioritize calling the management aggregation capability corresponding to
```
manage
```
.
Parameter Guide:
- ```
--users
```
  supports account numbers, Chinese names, and multiple users separated by commas.
- ```
--type
```
  supports
```
tasks/stories/bugs/all
```
  .
- The default scope is current unfinished items + items completed/closed today; if the user specifies a time window, append
```
--date-from
```
  and
```
--date-to
```
  .
- ```
--status
```
  supports comma separation, such as
```
doing,wait
```
  .
- ```
--deadline-from
```
  and
```
--deadline-to
```
  can be used to filter tasks due soon;
```
--overdue-only
```
  can be used to view only overdue items.
- The status in the management perspective is cross-type semantic mapping, not simple literal matching: for example,
```
doing,wait,done
```
  will automatically cover the corresponding pending/completed statuses of tasks, requirements, and bugs.
- ```
--team-name <team name>
```
  can directly reuse the locally cached team member list, suitable for daily patrols of fixed teams.
- The "total" in the output will strictly follow the current
```
--type
```
  query scope, and additional filter conditions will be displayed to avoid misinterpreting targeted queries as full statistics.
- ```
my tasks --assign <account>
```
  and
```
manage --users <member>
```
  are not the same: the former is the official assignment scope, while the latter is the management aggregation perspective.
- The output prioritizes using Chinese-friendly fields for direct user reading, and also facilitates the large model to generate morning reports, weekly reports, and follow-up summaries later.

2. 对话式任务派发 (Chat-to-Task)

2. Chat-to-Task Assignment

触发意图：用户说**“把网关排查的活儿发给李四，给半天时间”**，但未指明具体项目或迭代时。
调用动作：组合调用
```
getProjects
```
->
```
getActiveExecutions
```
-> (若无当期迭代则调用
```
createExecution
```
) -> 最后发起
```
createTask
```
。
参数指南：务必先明确当前的迭代/执行
```
execId
```
。如不确定，先查询项目列表及其下挂载的近期执行。如有必要跨月，可智能创建一个当月的新冲刺。派单时，可以直接传入真实的中文
```
name
```
、
```
assignee
```
和工时
```
estimate
```
（默认2小时）。底层已内置自动修补禅道必填项和账号映射转换。若是“从需求拆分任务”，可直接传
```
storyId + projectId
```
；CLI 会优先复用当月执行，若不存在则复制上个执行配置后自动创建。
补充约定：创建任务时可直接传
```
pri
```
和
```
desc
```
；若未传
```
pri
```
，默认按
```
3
```
级优先级创建。

Trigger Intent: Users say "Assign the gateway troubleshooting task to Li Si, give him half a day" without specifying the specific project or iteration.
Call Action: Combine calls
```
getProjects
```
->
```
getActiveExecutions
```
-> (call
```
createExecution
```
if there is no current iteration) -> finally initiate
```
createTask
```
.
Parameter Guide: Be sure to clarify the current iteration/execution
```
execId
```
first. If unsure, query the project list and its recently attached executions first. If necessary to cross months, intelligently create a new sprint for the current month. When assigning tasks, you can directly pass in the real Chinese
```
name
```
,
```
assignee
```
, and estimated hours
```
estimate
```
(default 2 hours). The underlying layer has built-in automatic patching of ZenTao required fields and account mapping conversion. If it is "split tasks from requirements", you can directly pass
```
storyId + projectId
```
; the CLI will prioritize reusing the current month's execution, and if it does not exist, it will copy the previous execution configuration and create it automatically.
Supplementary Agreement: You can directly pass
```
pri
```
and
```
desc
```
when creating a task; if
```
pri
```
is not passed, it will be created with priority level
```
3
```
by default.

3. 一句话快捷报工 (Seamless Effort Logging)

3. Seamless Effort Logging

触发意图：用户说**“给 10452 任务登记 2 个小时的内容撰写工时”**。
调用动作：调用
```
addEstimate
```
。
参数指南：必须带有精确的
```
taskId
```
、耗时
```
consumed
```
以及备注
```
work
```
。本接口底座已修复了禅道坑爹的报工幽灵丢失漏洞，直接确保工时准确入库！

Trigger Intent: Users say "Log 2 hours of content writing work for task 10452".
Call Action: Call
```
addEstimate
```
.
Parameter Guide: Must include the exact
```
taskId
```
, consumed time
```
consumed
```
, and remark
```
work
```
. This interface base has fixed ZenTao's annoying effort logging ghost loss vulnerability, directly ensuring accurate work hour storage!

4. 极简状态流转 (State Machine Control)

4. Minimalist State Transition

触发意图：用户说**“那个 Bug 修完了，状态转给测试组长张三”**。
调用动作：按实体类型调用
```
updateTask
```
、
```
updateStory
```
、
```
updateBug
```
工具组合。
检索补充：若用户只给了任务名称而没有给
```
taskId
```
，可先调用
```
findTasksByName
```
在当前账号、指定成员或团队范围内检索任务，拿到准确 ID 后再继续状态流转或报工。

Trigger Intent: Users say "That bug has been fixed, transfer the status to test team leader Zhang San".
Call Action: Call the tool combination
```
updateTask
```
,
```
updateStory
```
,
```
updateBug
```
according to the entity type.
Supplementary Retrieval: If the user only provides the task name but not the
```
taskId
```
, you can first call
```
findTasksByName
```
to retrieve the task within the current account, specified member, or team scope, and then proceed with state transition or effort logging after obtaining the accurate ID.

5. 智能链接提取 (Smart Link Resolver)

5. Smart Link Resolver

触发意图：用户在群聊或对话中甩出一条任意掺杂着链接的文本（如 **“帮我看看这个任务什么情况：http://zentao.yourcompany.com/task-view-123.html”**）。
调用动作：提取包含网址在内的整段内容传给底层解析封装。你可以依此瞬间掌握该链接指向的任务/缺陷/需求等一切核心骨干状态。

Trigger Intent: Users send a piece of text with any mixed links in group chats or conversations (such as "Help me check the status of this task: http://zentao.yourcompany.com/task-view-123.html").
Call Action: Pass the entire segment including the URL to the underlying layer for parsing and encapsulation. You can instantly grasp all core statuses of the task/defect/requirement pointed to by the link.

6. 派发前负荷参考雷达 (Workload Radar)

6. Workload Radar Before Assignment

触发意图：用户在派发新任务前问**"李四目前有多少任务在手上，还有多少工时要做？"，或者"帮我看看张三和李四谁比较空"**。
调用动作：调用底层
```
getMemberLoad
```
，传入一个或多个成员账号/中文名，并发拉取其处理中任务与剩余工时后统一汇报。
重要原则：这是纯参考数据，不应自动阻断或拒绝 派单操作。应将数据呈现给用户，由用户决定是否继续分派。
团队缓存补充：若用户已保存团队别名，可优先使用
```
--team-name
```
复用团队成员列表。
口径补充：该能力已复用管理视角底座，输出会显式标明是任务还是 Bug。
展示补充：输出中应包含
```
P1
```
未完成任务数量、任务平均进度，以及每条任务的单项进度百分比，帮助用户快速判断团队负荷质量。

Trigger Intent: Before assigning a new task, users ask "How many tasks does Li Si currently have, and how many hours of work are left?" or "Help me see who is more available between Zhang San and Li Si".
Call Action: Call the underlying
```
getMemberLoad
```
, pass in one or more member accounts/Chinese names, pull their ongoing tasks and remaining work hours concurrently, and report uniformly.
Important Principle: This is purely reference data, and should not automatically block or reject assignment operations. Present the data to the user and let the user decide whether to continue assigning.
Team Cache Supplement: If the user has saved a team alias, you can prioritize using
```
--team-name
```
to reuse the team member list.
Scope Supplement: This capability has reused the management perspective base, and the output will explicitly indicate whether it is a task or a bug.
Display Supplement: The output should include the number of unfinished
```
P1
```
tasks, the average progress of tasks, and the individual progress percentage of each task to help users quickly judge the quality of team workload.

7. 停滞单据排查 (Stagnant Tasks Patrol)

7. Stagnant Tasks Patrol

触发意图：用户询问**"张三有什么任务一直没动"** 或 "帮我看看团队里有没有什么任务超过一周没人管"。
调用动作：提取目标成员列表与停滞天数阈值（默认3天），调用
```
getStagnantTasks
```
返回按停滞时长排序的停滞单据清单。

Trigger Intent: Users ask "What tasks has Zhang San not been working on for a long time" or "Help me check if there are any tasks in the team that have been unattended for more than a week".
Call Action: Extract the target member list and stagnation day threshold (default 3 days), call
```
getStagnantTasks
```
to return a list of stagnant documents sorted by stagnation duration.

8. 晨会综合沙盘 (Morning Standup Radar)

8. Morning Standup Radar

触发意图：用户说**"帮我出今天的晨会通报"** 或 "看看今天团队有哪些紧急的事项"，并提供团队成员列表。
调用动作：调用
```
getMorningCheck
```
，传入团队成员列表，返回三类清单：
```
overdue
```
（已超期）、
```
dueSoon
```
（今明到期）、
```
highPriority
```
（高优悬空）。
输出要求：请将三类数据以清晰简明的格式呈现，使用 emoji 区分风险等级（🔴超期 / 🟡临期 / 🟠高优），方便用户直接转发晨会通报。
团队缓存补充：固定团队可先通过
```
team save
```
建立别名，后续晨会直接使用
```
--team-name
```
。
口径补充：该能力已复用管理视角底座，预警清单中会显式区分任务、需求、Bug。
过滤补充：无截止日期的需求默认不纳入晨会预警，避免将弱时效事项误判为晨会风险。
参数补充：支持通过
```
--pri-max
```
调整晨会关注的高优阈值，例如传
```
1
```
时仅保留
```
P1
```
事项；输出中同时展示粗粒度进度百分比，便于快速判断推进程度。

Trigger Intent: Users say "Help me generate today's morning standup report" or "See what urgent matters the team has today" and provide the team member list.
Call Action: Call
```
getMorningCheck
```
, pass in the team member list, and return three types of lists:
```
overdue
```
(already overdue),
```
dueSoon
```
(due today or tomorrow),
```
highPriority
```
(high-priority pending).
Output Requirements: Present the three types of data in a clear and concise format, use emojis to distinguish risk levels (🔴 Overdue / 🟡 Due Soon / 🟠 High Priority), so that users can directly forward the morning standup report.
Team Cache Supplement: Fixed teams can first establish an alias through
```
team save
```
, and directly use
```
--team-name
```
for subsequent morning standups.
Scope Supplement: This capability has reused the management perspective base, and the warning list will explicitly distinguish between tasks, requirements, and bugs.
Filter Supplement: Requirements without deadlines are not included in the morning standup warning by default to avoid misjudging low-time-sensitive matters as morning standup risks.
Parameter Supplement: Supports adjusting the high-priority threshold for morning standup attention via
```
--pri-max
```
, for example, passing
```
1
```
only retains
```
P1
```
items; the output also displays coarse-grained progress percentages to facilitate quick judgment of progress.

9. 自动化周报摘要 (Weekly Synthesis)

9. Automated Weekly Synthesis

触发意图：用户说**"帮我出本周周报素材"、"汇总团队这周交付了哪些重点事项"**，并提供团队成员列表或团队名。
调用动作：调用
```
getWeeklySynthesis
```
，传入团队成员列表与时间窗，返回两类核心清单：
```
stories
```
（高优需求交付）与
```
bugs
```
（重大缺陷修复），同时附带成员维度交付汇总。
输出要求：优先展示统计范围、本周截止窗口、
```
总交付 / 高优交付 / 本周待完成任务
```
与成员交付汇总；仅在用户明确需要逐条清单时，再补充任务、需求、Bug 详情。
团队缓存补充：固定团队优先通过
```
team save
```
建立别名，周报直接复用
```
--team-name
```
。
参数补充：支持
```
--date-from
```
、
```
--date-to
```
自定义统计窗口，支持
```
--pri-max
```
收敛到更高价值的交付事项；Bug 严重程度默认跟随该阈值，
```
--severity-max
```
仅保留为兼容补充参数。
视图补充：支持
```
--view summary|full
```
，默认使用
```
summary
```
。当用户只需要给大模型投喂底稿时，直接走默认值；当用户明确需要逐条清单时，再切换为
```
full
```
。
周窗口补充：周报会按自然周自动识别周一到周日；即使在周四、周五、周六查询，也会自动纳入本周周末截止但尚未完成的任务。

Trigger Intent: Users say "Help me generate this week's weekly report materials", "Summarize the key items delivered by the team this week" and provide the team member list or team name.
Call Action: Call
```
getWeeklySynthesis
```
, pass in the team member list and time window, and return two types of core lists:
```
stories
```
(high-priority requirement delivery) and
```
bugs
```
(major defect fixes), along with member-level delivery summaries.
Output Requirements: Prioritize displaying the statistical scope, this week's deadline window,
```
total delivery / high-priority delivery / pending tasks this week
```
and member delivery summaries; only when the user explicitly needs itemized lists, supplement the details of tasks, requirements, and bugs.
Team Cache Supplement: Fixed teams prioritize establishing an alias through
```
team save
```
, and directly reuse
```
--team-name
```
for weekly reports.
Parameter Supplement: Supports
```
--date-from
```
and
```
--date-to
```
to customize the statistical window, supports
```
--pri-max
```
to converge to higher-value delivery items; the bug severity level follows this threshold by default, and
```
--severity-max
```
is only retained as a compatible supplementary parameter.
View Supplement: Supports
```
--view summary|full
```
, defaults to
```
summary
```
. When the user only needs to provide draft materials to the large model, use the default value directly; when the user explicitly needs itemized lists, switch to
```
full
```
.
Week Window Supplement: The weekly report will automatically recognize Monday to Sunday according to the natural week; even if queried on Thursday, Friday, or Saturday, it will automatically include tasks that are due this weekend but not yet completed.

💻 安全与环境依赖说明 (Environment & Security)

💻 Environment & Security Notes

⚠️ 运行须知： 这是一个受限的主流大模型端桥接应用。为保障您的操作合规，本扩展不会在未授权状态下进行任何风险调优或系统篡改。

⚠️ Usage Notice: This is a restricted mainstream large model end-bridging application. To ensure your operational compliance, this extension will not perform any risk tuning or system tampering without authorization.

1. 安装与依赖引入

1. Installation & Dependency Introduction

如果您需要在本地命令行使用或验证此工具，可以进行全局安装或扩展装载：

bash

undefined

If you need to use or verify this tool in the local command line, you can install it globally or load it as an extension:

bash

undefined

全局安装 CLI 工具

npm install -g @chenish/zentao-mcp-agent

或者通过 npx 挂载大模型工具 (如平台需要)

npx skills add @chenish/zentao-mcp-agent


作为环境依赖底座，首次使用必须执行授权鉴权：
```bash
zentao-cli login --url "https://xxxxx.com/zentao" --account "<账号>" --pwd "<密码>"

npx skills add @chenish/zentao-mcp-agent


As an environment dependency base, authorization authentication must be performed for the first use:
```bash
zentao-cli login --url "https://xxxxx.com/zentao" --account "<账号>" --pwd "<密码>"

2. 命令行全量调用实例

2. Full Command Line Call Examples

本插件已将极其复杂的禅道 API 与路由封装为极简的指令集，可用作日常 CLI：

🔥 地盘全视界 (My Dashboard)

bash

undefined

This plugin has encapsulated the extremely complex ZenTao API and routing into a minimalist command set, which can be used as a daily CLI:

🔥 My Dashboard

bash

undefined

基础：默认拉取指派给我的待办任务

zentao-cli my tasks

分类：拉取指派给我的缺陷清单

zentao-cli my bugs

分类：拉取指派给我的需求清单 (聚合：一键获取我名下的业务需求)

zentao-cli my stories

管理视角：跨权限查看张三地盘上的所有任务 (查岗：跨项目查阅张三的任务列表)

zentao-cli my tasks --assign 张三

精准过滤：查看张三目前正在进行中的任务 (过滤：精确提取张三进行中的代办)

zentao-cli my tasks --assign 张三 --status doing

管理聚合视角：汇总张三当前相关的任务、需求、缺陷

zentao-cli manage --users 张三

管理聚合视角：只看团队成员当前任务池

zentao-cli manage --users 张三,李四 --type tasks

管理聚合视角：只看单人的缺陷

zentao-cli manage --users 张三 --type bugs

管理聚合视角：只看进行中的任务

zentao-cli manage --users 张三 --type tasks --status doing

管理聚合视角：同时看进行中与待开始任务

zentao-cli manage --users 张三 --type tasks --status doing,wait

团队缓存视角：直接按团队名查询

zentao-cli manage --team-name "规划组"

时间窗管理视角：补入指定日期内完成/关闭的任务

zentao-cli manage --users 张三,李四 --date-from 2026-03-12 --date-to 2026-03-12

临期任务视角：筛出周末前到期任务

zentao-cli manage --users 张三,李四 --type tasks --deadline-to 2026-03-16

风险视角：只看已延期任务

zentao-cli manage --users 张三,李四 --type tasks --overdue-only

团队缓存管理

zentao-cli team save --name "规划组" --users "张三,李四,王五" zentao-cli team list zentao-cli team show --name "规划组" zentao-cli team delete --name "规划组"

团队缓存晨会：只看 P1 高优事项

zentao-cli morning-check --team-name "规划组" --pri-max 1

团队缓存负荷：查看 P1 数量与任务进度

zentao-cli load --team-name "规划组"

团队缓存周报：输出本周高优需求与重大缺陷修复

zentao-cli weekly-synthesis --team-name "规划组"

自定义时间窗周报

zentao-cli weekly-synthesis --team-name "规划组" --date-from 2026-03-09 --date-to 2026-03-13 --pri-max 1

摘要模式周报：仅输出统计与重点摘要

zentao-cli weekly-synthesis --team-name "规划组" --view summary

详情模式周报：输出完整任务、需求、Bug 清单

zentao-cli weekly-synthesis --team-name "规划组" --view full


**🔥 对话派单化与执行自治 (Projects & Chat-to-Task)**
```bash

zentao-cli weekly-synthesis --team-name "规划组" --view full


**🔥 Chat-to-Task & Execution Autonomy**
```bash

列出活跃中的项目总库 (新增能力)

zentao-cli projects

获取某项目下活跃的冲刺/迭代 ID 列表 (历史意图示例，当前 CLI 参数请使用 --projectId)

zentao-cli executions --project 577

获取某项目下活跃的冲刺/迭代 ID 列表 (当前 CLI 参数)

zentao-cli executions --projectId 577

仅看进行中的迭代

zentao-cli executions --projectId 577 --status doing

当期无迭代时：自动新建一个默认7天的本月新冲刺阶段

zentao-cli execution create --projectId 577 --name "2026年3月常规迭代"

显式指定起止日期创建迭代

zentao-cli execution create --projectId 577 --name "2026年3月常规迭代" --begin "2026-03-17" --end "2026-03-24"

指定工作日天数

zentao-cli execution create --projectId 577 --name "2026年3月常规迭代" --days 6

瞬时派单：时间与工时全部由底层静默注入默认值

zentao-cli task create --execId 123 --name "网关熔断排查" --assign "张三"

带优先级与描述派单

zentao-cli task create --execId 123 --name "网关熔断排查" --assign "张三" --pri 2 --desc "补充任务描述"

精细派单：明确指定 8 小时预估工时和特定截止日期

zentao-cli task create --execId 123 --name "全量压测" --assign "李四" --estimate 8 --deadline "2026-03-20"

指定预估工时，截止日期走默认值

zentao-cli task create --execId 123 --name "接口联调" --assign "张三" --estimate 4

从需求拆分任务：自动复用当月执行，必要时复制上个执行后建任务

zentao-cli task create --storyId 12072 --projectId 281 --name "数据库改造脚本适配" --assign "张三" --estimate 8 --pri 2

从需求拆分任务：显式指定执行模板与新执行名称

zentao-cli task create --storyId 12072 --projectId 281 --templateExecId 5825 --executionName "2026年03月常规迭代" --name "数据库改造脚本适配" --assign "张三" --desc "从需求拆分的研发任务"


**🔥 单点状态机 (State Machine Control)**
```bash

zentao-cli task create --storyId 12072 --projectId 281 --templateExecId 5825 --executionName "2026年03月常规迭代" --name "数据库改造脚本适配" --assign "张三" --desc "从需求拆分的研发任务"


**🔥 State Machine Control**
```bash

状态扭转：仅将任务状态标记为已完成

zentao-cli task update --taskId 123 --status done

先按名称找任务 ID

zentao-cli task find --name "网关排查"

在指定成员范围内按名称找任务

zentao-cli task find --name "接口联调" --owner zhangsan,lisi

在团队缓存范围内按名称找任务

zentao-cli task find --name "接口联调" --team-name "规划组"

启动任务：切换为进行中

zentao-cli task update --taskId 123 --status doing --comment "开始处理"

关闭任务：验证完成后关闭

zentao-cli task update --taskId 123 --status closed --comment "验证通过，执行关闭"

任务转交：仅将任务丢给张三处理

zentao-cli task update --taskId 123 --assign 张三

复合协同：完成、转交、加备注一气呵成

zentao-cli task update --taskId 123 --status done --assign 张三 --comment "代码已提交，转交测试验证"

关闭需求：将需求直接关闭

zentao-cli story update --storyId 12072 --status closed --comment "需求已验收完成"

激活需求：将已关闭需求重新激活

zentao-cli story update --storyId 14526 --status active --comment "重新激活继续推进"

转交需求：将需求交给张三继续跟进

zentao-cli story update --storyId 12072 --assign 张三 --comment "转交继续跟进"

解决缺陷：将 Bug 标记为已解决

zentao-cli bug update --bugId 11071 --status done --comment "缺陷已修复完成"

关闭缺陷：验证通过后关闭 Bug

zentao-cli bug update --bugId 11071 --status closed --comment "验证通过，关闭缺陷"

重开缺陷：继续跟踪处理

zentao-cli bug update --bugId 11071 --status active --comment "重新激活继续跟踪"

转交缺陷：将 Bug 交给张三继续跟进

zentao-cli bug update --bugId 11071 --assign 张三 --comment "转交继续跟进"


**🔥 一句话报工作业 (Log Effort)**
```bash

zentao-cli bug update --bugId 11071 --assign 张三 --comment "转交继续跟进"


**🔥 Seamless Effort Logging**
```bash

极简报工：给 69704 任务快速登记 2 小时消耗

zentao-cli task effort --taskId 69704 --consumed 2

详尽报工：登记耗时并追加详细的研发日志

zentao-cli task effort --taskId 69704 --consumed 2.5 --desc "完成了核心业务逻辑的编写"


> 当前 `task effort` CLI 已稳定支持 `--taskId + --consumed`，可选 `--desc`；仅写说明不填耗时仍属于后续增强目标。

**当前已知限制**
- `task effort --taskId <id> --desc "..."` 这种仅写说明不填耗时的形态，在当前禅道环境中页面历史不会稳定落备注。
- `story update --storyId <id> --status active` 在当前禅道环境中尚未稳定生效，需求激活链路仍待后续排查。

---

zentao-cli task effort --taskId 69704 --consumed 2.5 --desc "完成了核心业务逻辑的编写"


> 当前 `task effort` CLI 已稳定支持 `--taskId + --consumed`，可选 `--desc`；仅写说明不填耗时仍属于后续增强目标。

**Current Known Limitations**
- The form of `task effort --taskId <id> --desc "..."` which only writes remarks without filling in consumed time will not stably save remarks in the page history in the current ZenTao environment.
- `story update --storyId <id> --status active` has not yet taken effect stably in the current ZenTao environment, and the requirement activation link is still to be investigated later.

---

🤝 欢迎提出需求与共建

🤝 Welcome to Submit Requirements and Collaborate

如果你对本插件有任何新的期待，或者希望由社区帮你加入更多针对禅道系统的定制化、自动化功能接口，我们非常愿意并且乐意为大家拓展功能！欢迎随时前往 GitHub Repository 提交你的 Issue 需求或者 Bug 报错。

If you have any new expectations for this plugin, or hope that the community will help you add more customized and automated function interfaces for the ZenTao system, we are very willing and happy to expand the functions for everyone! Welcome to submit your Issue requirements or bug reports to the GitHub Repository at any time.

zentao

Original

Translation

ZenTao AI Assistant (zentao-mcp-agent)

ZenTao AI Assistant (zentao-mcp-agent)

When to use this skill

When to use this skill

💡 AI 最佳实践指引 (For LLM AI)

💡 AI Best Practice Guidelines (For LLM AI)

1. 全视界地盘拉取 (Global Dashboard)

1. Global Dashboard Pull

1.1 管理聚合视角补充规则 (Management Dashboard)

1.1 Supplementary Rules for Management Aggregation View

2. 对话式任务派发 (Chat-to-Task)

2. Chat-to-Task Assignment

3. 一句话快捷报工 (Seamless Effort Logging)

3. Seamless Effort Logging

4. 极简状态流转 (State Machine Control)

4. Minimalist State Transition

5. 智能链接提取 (Smart Link Resolver)

5. Smart Link Resolver

6. 派发前负荷参考雷达 (Workload Radar)

6. Workload Radar Before Assignment

7. 停滞单据排查 (Stagnant Tasks Patrol)

7. Stagnant Tasks Patrol

8. 晨会综合沙盘 (Morning Standup Radar)

8. Morning Standup Radar

9. 自动化周报摘要 (Weekly Synthesis)

9. Automated Weekly Synthesis

💻 安全与环境依赖说明 (Environment & Security)

💻 Environment & Security Notes

1. 安装与依赖引入

1. Installation & Dependency Introduction

全局安装 CLI 工具

全局安装 CLI 工具

或者通过 npx 挂载大模型工具 (如平台需要)

或者通过 npx 挂载大模型工具 (如平台需要)

2. 命令行全量调用实例

2. Full Command Line Call Examples

基础：默认拉取指派给我的待办任务

基础：默认拉取指派给我的待办任务

分类：拉取指派给我的缺陷清单

分类：拉取指派给我的缺陷清单

分类：拉取指派给我的需求清单 (聚合：一键获取我名下的业务需求)

分类：拉取指派给我的需求清单 (聚合：一键获取我名下的业务需求)

管理视角：跨权限查看张三地盘上的所有任务 (查岗：跨项目查阅张三的任务列表)

管理视角：跨权限查看张三地盘上的所有任务 (查岗：跨项目查阅张三的任务列表)

精准过滤：查看张三目前正在进行中的任务 (过滤：精确提取张三进行中的代办)

精准过滤：查看张三目前正在进行中的任务 (过滤：精确提取张三进行中的代办)

管理聚合视角：汇总张三当前相关的任务、需求、缺陷

管理聚合视角：汇总张三当前相关的任务、需求、缺陷

管理聚合视角：只看团队成员当前任务池

管理聚合视角：只看团队成员当前任务池

管理聚合视角：只看单人的缺陷

管理聚合视角：只看单人的缺陷

管理聚合视角：只看进行中的任务

管理聚合视角：只看进行中的任务

管理聚合视角：同时看进行中与待开始任务

管理聚合视角：同时看进行中与待开始任务

团队缓存视角：直接按团队名查询

团队缓存视角：直接按团队名查询

时间窗管理视角：补入指定日期内完成/关闭的任务

时间窗管理视角：补入指定日期内完成/关闭的任务

临期任务视角：筛出周末前到期任务

临期任务视角：筛出周末前到期任务

风险视角：只看已延期任务

风险视角：只看已延期任务

团队缓存管理

团队缓存管理

团队缓存晨会：只看 P1 高优事项

团队缓存晨会：只看 P1 高优事项

团队缓存负荷：查看 P1 数量与任务进度

团队缓存负荷：查看 P1 数量与任务进度

团队缓存周报：输出本周高优需求与重大缺陷修复

团队缓存周报：输出本周高优需求与重大缺陷修复

自定义时间窗周报

自定义时间窗周报

摘要模式周报：仅输出统计与重点摘要

摘要模式周报：仅输出统计与重点摘要

详情模式周报：输出完整任务、需求、Bug 清单