Write reusable operating procedures for recurring business tasks and handovers. Organize prerequisites, roles, steps, success checks, and exception handling, while clearly separating approved recovery actions from decisions that still need confirmation.
为重复性业务任务编写可复用的操作手册，涵盖前置条件、具体步骤、结果验证、失败处理和升级路径。适用于周期性工作或交接操作指引。
Review the instructions the agent will receive before you install.
帮助接手者完成用户指定的一次操作或交接。先确定本次终点：交接完成不等于下游发布、使用或项目全部完成。
终点用于限定手册范围，输出中不另设“本次终点”段重复后面的成功判据。
只写给定正常步骤、完整成功判据和所问异常。正常步骤保留角色、频率、输入、核验与交付点，必要未知参数就地占位。成功判据只含用户给出的检查；未要求的打开、可读、无乱码、失败留痕和当日上报均标为建议。成功判据包括已知检查和交接，并排除每一种所问异常，不增加未要求的下游操作。例（虚构）：总额正确但凭证重复，仍不能正常结案。异常发现环节未知，仅该环节待确认，不能省去异常判断。
总结性成功判据只在一处完整列出；步骤按执行顺序写，但每步仍须就地写明执行所必需的前置条件、判断门槛和保护点，即使这会与总结判据重合。例如，“仅在行数一致时保存”应写在保存步骤中。必要时可简短引用已列判据；不能为避免重复而删掉执行门槛。标题不复述终点，结尾不复制成功判据或重复待确认参数。每个异常分支只写该分支特有的识别、恢复和交接信息。
例（虚构）：“助理上传已审核稿，核对预览后交编辑；编辑有发布权。”本次手册的成功是上传确认、预览通过、交编辑，不能要求编辑发布后才算助理交接完成。
先列已授处置，再列待定恢复，分开表达：
| 已知范围 | 分支中的处置 |
|---|---|
| 已授暂停、保留原件等 | 直接沿用已授动作，不重新索取该动作权限。 |
| 恢复方式或权限未给 | 写“恢复方案待确认：〔具体缺项〕；确认后按获批方案执行”。 |
| 用户要求设计恢复方案 | 单列“建议方案”，说明条件与待采纳参数，不冒充现行步骤。 |
重做、重传、重新导出都是恢复执行。次数或权限未知时，不能在一个分支先写“核实后重新生成”，再靠下一句“次数待确认”补救。正常流程执行一次与异常后重复执行区分开。
例（虚构）：“核对清单后归档；核对不一致，重制权限和次数未给。”异常可写“差异及恢复方案待确认（重制权限、次数）；确认后按获批方案执行”。不能写“核实后重新制作并核对，再确认重制次数”。必要的新增暂停、留档或升级动作，未获授权时标为建议，接收角色未知就地留缺。
输出前单独走一遍每个分支：已知成功条件全部保留，未定恢复没有提前执行，已给参数前后不矛盾。未知的恢复权限与次数按各分支获批方案的适用范围分别确认，不能因占位名称相同就推定共用授权或次数。最后一个必要分支结束即结束，不追加参数一致性说明；复杂交接才补展开参数、审计及失败推演。编写手册不等于实际操作。
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review a design or web page against WCAG 2.1 AA, an accessibility standard. Organize findings on contrast, keyboard access, forms, and screen reader behavior, with severity levels and practical recommendations for fixes.
Retrieve financial data for Chinese markets and selected global markets using akshare-cli. Find stock prices, fund values, exchange rates, economic indicators, and financial news, then extract recent records or save results in common file formats.
Compare technology options, review a system design, or plan a new component from requirements and constraints. The skill organizes the reasoning into an architecture decision record, a document covering alternatives, trade-offs, consequences, and next steps.
Turn existing or proposed business processes into reusable standard operating procedures. Organize steps, roles, conditions, and known exceptions while marking missing details, producing clear handover documents without inventing approvals or responsibilities.
Analyze waiting, rework, and handoff waste in business processes using the facts provided. It proposes concrete improvements and, when verification is needed, defines measurement formulas and the minimum records required to assess specific issues.
Assess operational risks in processes, projects, or suppliers using provided evidence. Separate observed facts from possible consequences, propose practical responses, and prepare concise summaries or risk registers without treating unknown controls as confirmed gaps.