Fortesters releasing a version: enter the Yunxiaoiteration name → pull the requirements linked to that iteration → automatically generate the external version update log.
You can also manually paste a change list (fallback).Estimated maintenance durationis notified separately by a person and is not written into the log.
When to use
- Testers say:
按 $AutoVUL/生成版本更新日志/按迭代 xxx 出更新日志 - Input contains a Yunxiao "iteration name"
- Need a unified wording standard before release
Main flow (testers · by iteration, default)
See for the complete data retrieval steps references/yunxiao-sprint.md。
1. 确认云效项目（缺省：统一运营管理平台PC端；可改）
2. 向用户索取「迭代名称」（若口令里已带则直接用）
3. 在云效查找该迭代 → 立即反馈成功或失败（见下）
4. 成功：列出迭代内关联「需求」清单（编号 + 标题 + 状态）供用户快速核对
5. 从每条需求提取变更素材（优先级见「素材优先级」）
6. 按本文格式分类、合并、润色 → 输出成稿正文
Iteration retrieval · success / failure feedback (mandatory)
After finding the iteration,must give feedback first, then continue or stop:
| Result | Feedback text (may be slightly adjusted, semantics unchanged) | Next step |
|---|---|---|
| Exactly 1 iteration matched | ✅ 已找到迭代「{名称}」（状态：{状态}），关联需求 {N} 条。 |
Continue pulling requirements and generate |
| 0 matches | ❌ 未找到迭代「{输入}」。请核对后重新输入迭代名称（可复制云效迭代标题）。 |
Stop generation; wait for the user to re-enter |
| Multiple fuzzy matches | ⚠️ 找到多个相似迭代：1)… 2)… 请回复序号或完整精确名称。 |
Wait for the user to select before continuing |
| Login/permission failure | ❌ 无法访问云效（未登录或无权限）。请在浏览器登录云效后重试，或改用手动清单。 |
Stop; prompt to log in or use the fallback |
| Iteration exists but has 0 requirements | ⚠️ 迭代「{名称}」已找到，但暂无关联需求。请确认规划后再试，或改用手动清单。 |
Stop generating the external body |
After failure: the user only needs to send the iteration name again (or correct the project name) and rerun from step 2; do not ask the user to reinstall the Skill.
Material priority (per requirement)
| Order | Source | Usage |
|---|---|---|
| 1 | The "Update content" section in the requirement description (not "Update content · history") | First choice; directly rewrite into log entries |
| 2 | The externally shareable part of the "Feature change record" in AutoPRD | Second choice |
| 3 | Requirement title + short description summary | Only when both of the above are empty; value sentences may be reasonably completed |
| — | Pure technical debt, internal monitoring, not opened to users | Do not write intothe external log |
Bug-type requirements (type/tag contains defect fix, or the update content says "fix") go under [Bug Fixes]; the rest go under [New Features]. When the boundary is unclear, prefer Bug Fixes.
Version number and update time
| Field | Rule |
|---|---|
| Version number | Prefer parsing from the iteration name (e.g. if it contains V1.1.5 / 1.1.5); if it cannot be parsed, ask the user |
| Update time | Use it if the user provides it; if not provided, you may write the iteration planned start date's MM月DD日HH:MM, or ask first |
| Product line | Default OneOS PC版 |
Fallback flow (manual list)
When there is no Yunxiao permission, or the iteration is empty: use input-template.md to paste the list, skip the iteration step, and directly classify and polish.
Fixed output format
OneOS PC版V{主.次.修订}更新日志：
更新时间：{MM}月{DD}日{HH}:{MM}
----------------------------------------------------
【新功能】
1「{模块名}」{做了什么}，{责任部门}可{用户价值 / 解决的问题}
2「{模块名}」{…}
【Bug修复】
3「{模块名}」{修复了什么}，{责任部门}可{恢复的能力 / 避免的影响}
Hard layout constraints
| Item | Rule |
|---|---|
| Title | OneOS PC版V + Version number + 更新日志：(e.g. V1.1.5, no spaces) |
| Update time | Start time only;MM月DD日HH:MM；Prohibited"Expected to complete within x minutes" |
| Separator line | ---------------------------------------------------- |
| Section | Only 【新功能】 / 【Bug修复】; omit the entire segment if the category is empty |
| Sequence number | Continuous throughout, starting from 1 |
| Module name | 「」; consistent with the official product menu name |
| External body text | Do not writerequirement numbers, defect numbers, iteration IDs (the checklist may be attached separately) |
| Ending | No signature, no "Thank you for using", no technical appendix |
Classification / Merging / Copywriting (final draft rules)
| Classify under [New Features] | Classify under [Bug Fixes] | Do not write into the external log |
|---|---|---|
| New capabilities, new entry points, new fields/flows, perceptible experience optimizations | Abnormalities in existing capabilities, errors, data errors, interaction failures | Technical debt, imperceptible performance, unreleased gray-scale, internal monitoring only |
- Same section, same moduleMerge into one item, use for sub-points
； - Cross-sectionWrite one item each for the same module in different columns
- Each item includes: what it does + user value + natural embedding of the responsible department (
{部门}人员可…） - Prohibited"For use by ... line ..."; department mapping module-role-mapping.md
- Do not fabricate capabilities that do not exist in the iteration; if in doubt, skip or mark as pending confirmation (not included in the formal final draft)
- Recommended length per item ≤100 characters
Ordering: new features before fixes; within the same section, all-user impact first; funding/compliance fixes placed at the very front of the fixes section.
Output discipline
- Firstoutput the iteration reading feedback (✅/❌/⚠️)
- On success: you may first provide a short "Requirement List for This Iteration" table (including numbers, for test verification)
- Then outputplain-text final draft body(by default, do not wrap the final draft with a Markdown top-level heading)
- When explicitly requested by the user, you may append "Classification Basis / Skipped Items" after the body
Pre-release self-check
- Iteration search results have been fed back; when failed, no final draft was forcibly fabricated
- All final draft items can be traced back to the requirement materials associated with this iteration
- Title, time line, and separator line are correct; no estimated duration
- Merging of the same module is correct; each item includes value + natural embedding of the department
- The external body text has no requirement numbers/defect numbers/technical jargon; sequence numbers are continuous
Instructions for testing colleagues
按 $AutoVUL 生成版本更新日志。
项目：统一运营管理平台PC端
迭代名称：V1.1.5发版迭代
更新时间：07月16日16:00
If the iteration name is written incorrectly, just correct it as prompted and send it again.
For manual fallback, see input-template.md; for a final draft example, see examples.md。