Back to Details

zeno-reporting-discovered-tasks

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Reporting Discovered Tasks (Contributor Workflow)

报告发现的额外任务（贡献者工作流）

Overview

概述

During task execution, you may discover additional work that's needed but not in your current task. Report these discoveries to ZŌE for review instead of expanding your current task scope.
Trigger: Found work that:
  • Is not in current task description
  • Is needed for project success
  • Would expand current task scope
Output: Discovery report in Nexus for ZŌE review
在任务执行过程中，你可能会发现当前任务中未包含但需要完成的额外工作。请将这些发现报告给ZŌE进行审核，而非直接扩大当前任务的范围。
触发场景： 发现以下类型的工作时：
  • 未包含在当前任务描述中
  • 对项目成功至关重要
  • 会扩大当前任务的范围
输出要求： 在Nexus中提交发现报告，供ZŌE审核

When to Report (vs. Just Do It)

何时报告（vs. 直接处理）

Report to ZŌE when:
  • Work is clearly outside current task scope
  • Might be already planned elsewhere
  • Uncertain if actually needed (YAGNI check)
  • Large enough to be its own task
  • Blocks your current work but not your responsibility
Just do it (in current task) when:
  • Small addition (< 10 min)
  • Clearly required for your task to complete
  • No design decisions needed
  • Won't expand scope significantly
Use judgment: When in doubt, report. ZŌE can always say "include it."
需向ZŌE报告的情况：
  • 工作明显超出当前任务范围
  • 可能已在其他地方规划
  • 不确定是否真的需要（YAGNI原则检查）
  • 工作量足够大，可作为独立任务
  • 阻碍当前工作但不属于你的职责范围
可直接在当前任务中处理的情况：
  • 小改动（耗时<10分钟）
  • 明确是完成当前任务的必要条件
  • 无需做出设计决策
  • 不会显著扩大任务范围
判断原则： 如有疑问，优先报告。ZŌE可以决定是否将其纳入当前任务。

Discovery Report Structure

发现报告结构

Use 
probe discover report
:
bash
probe discover report \
  --task <current-task-id> \
  --project <project-id> \
  --title "[Clear action description]" \
  --type [bug|improvement|feature] \
  --severity [low|medium|high|critical]
使用
probe discover report
命令：
bash
probe discover report \
  --task <current-task-id> \
  --project <project-id> \
  --title "[清晰的行动描述]" \
  --type [bug|improvement|feature] \
  --severity [low|medium|high|critical]

Report Quality Checklist

报告质量检查清单

Before submitting:
  1. Search existing tasks - Is this already reported?
    • Check task queue for similar items
    • Avoid duplicates
  2. Check current task - Is this actually out of scope?
    • Re-read your task description
    • Sometimes it's within scope, just not obvious
  3. Clear description - Can ZŌE understand without your context?
    • What you were doing
    • What you found
    • Why it matters
  4. Appropriate severity:
    • Critical - Blocks current work, system broken
    • High - Should be done soon, significant impact
    • Medium - Nice to have, moderate impact
    • Low - Minor improvement, small impact
提交前需确认：
  1. 搜索现有任务 - 是否已有人报告过？
    • 检查任务队列中是否有类似条目
    • 避免重复报告
  2. 核对当前任务 - 这是否真的超出范围？
    • 重新阅读你的任务描述
    • 有时它其实在范围内，只是不够明显
  3. 描述清晰 - ZŌE无需你的上下文就能理解吗？
    • 你当时正在做什么
    • 你发现了什么
    • 为什么这很重要
  4. 严重程度恰当：
    • Critical（严重） - 阻碍当前工作，系统故障
    • High（高） - 应尽快处理，影响重大
    • Medium（中） - 锦上添花，影响中等
    • Low（低） - 微小改进，影响较小

Examples

示例

Good Discovery Report:
Context: Working on Task #42 (Add user validation), implementing 
         email format check in backend/src/validators/user.ts

Discovery: The password validation is scattered across 3 files 
           with inconsistent rules. No single source of truth.

Why Needed: If we fix email validation but leave password as-is,
            we have inconsistent security posture. Should consolidate.

Impact: Inconsistent validation leads to security holes and 
        maintenance burden. Every auth change touches 3+ files.

Severity: Medium
Priority: 3
Bad Discovery Report:
Found some stuff that needs fixing in the auth code.
Should probably clean it up.
Severity: Medium
优秀的发现报告示例：
背景：正在处理任务#42（添加用户验证），在backend/src/validators/user.ts中实现邮箱格式校验

发现：密码校验规则分散在3个文件中，规则不一致，没有单一的可信数据源。

必要性：如果我们修复了邮箱验证但保留密码校验现状，会导致安全策略不一致。应整合校验规则。

影响：不一致的验证会导致安全漏洞和维护负担。每次修改认证逻辑都要改动3个以上文件。

严重程度：Medium
优先级：3
不合格的发现报告示例：
发现认证代码里有些需要修复的问题。
可能应该清理一下。
严重程度：Medium

After Reporting

报告后的操作

Continue your current task:
  • Don't wait for ZŌE decision
  • Assume discovery won't be part of your current work
  • Complete your assigned task as scoped
Possible outcomes:
  1. Approved → New task created, you can claim it if you want
  2. Rejected → ZŌE explains why not needed, you learned
  3. Escalated → Becomes idea, you can vote on it
继续当前任务：
  • 无需等待ZŌE的决策
  • 默认发现的工作不会纳入当前任务
  • 按原范围完成分配的任务
可能的结果：
  1. 通过 → 创建新任务，你可以选择认领
  2. 拒绝 → ZŌE解释无需处理的原因，你可以从中学习
  3. 升级 → 成为创意提案，你可以参与投票

Anti-Patterns

反模式

❌ Wrong: Include discovered work in current task scope creep ✅ Right: Report it, let ZŌE decide if it's separate task
❌ Wrong: Vague description: "found some issues" ✅ Right: Specific: "inconsistent validation across 3 files"
❌ Wrong: Every small thing discovered gets reported ✅ Right: Judgment - report scope expansions, do small necessities
❌ Wrong: Assume discovered work is highest priority ✅ Right: Let ZŌE assess priority in context of all work
❌ Wrong: Stop current task to wait for discovery review ✅ Right: Continue current task, review happens async
❌ 错误做法： 将发现的工作纳入当前任务，导致范围蔓延 ✅ 正确做法： 报告给ZŌE，由其决定是否作为独立任务
❌ 错误做法： 描述模糊：“发现一些问题” ✅ 正确做法： 具体明确：“3个文件中的校验规则不一致”
❌ 错误做法： 发现所有小事都报告 ✅ 正确做法： 合理判断 - 报告范围扩张类工作，直接处理小的必要事项
❌ 错误做法： 假设发现的工作优先级最高 ✅ 正确做法： 由ZŌE结合整体工作评估优先级
❌ 错误做法： 暂停当前任务等待审核结果 ✅ 正确做法： 继续当前任务，审核异步进行

Remember

注意事项

  • Scope discipline - Your task is your task
  • Don't assume - What you found might not be needed
  • Clear context - ZŌE wasn't there, explain fully
  • Continue working - Don't block on review
  • Learn from feedback - ZŌE's decision teaches you what matters
  • 范围纪律 - 你的任务就是原分配的任务
  • 不要假设 - 你发现的内容可能并非必需
  • 清晰的上下文 - ZŌE不在现场，需完整解释
  • 继续工作 - 不要因审核而停滞
  • 从反馈中学习 - ZŌE的决策会让你了解什么是重点

Integration

流程衔接

Previous: You're using 
zeno-executing-tasks
skill Current: Found something outside scope Next: This skill reports it, then back to 
zeno-executing-tasks
to complete original work
ZŌE side: Uses 
zoe-reviewing-discovered-tasks
skill to review your report
上一步： 你正在使用
zeno-executing-tasks
技能 当前： 发现超出范围的内容 下一步： 使用此技能报告，然后回到
zeno-executing-tasks
完成原任务
ZŌE端： 使用
zoe-reviewing-discovered-tasks
技能审核你的报告