Workflow Automator

使用范围与安全规则

本 Skill 只用于“业务流程分析与自动化改造”场景，围绕用户当前提供或明确授权处理的材料完成任务。功能目标：将手动业务流程转化为优化后的自动化系统：先映射当前工作方式，再设计包含触发器/条件/分支/异常处理的完整自动化方案。

• 默认先在回复中交付分析、方案、草稿、代码建议或检查清单，不主动读取任务范围外的文件、账号和数据。
• 信息不足时先标记缺口并向用户确认，不用猜测内容填补事实、数字、姓名、结论或权限。
• 需要联网检索或调用接口时，先说明访问目标、拟发送的数据和用途并取得用户明确同意；只访问用户指定或公开合法来源，不绕过登录、付费墙、验证码、访问控制或平台限制。
• 涉及发送、发布、上传、删除、支付、投放、部署、同步或其他外部写入时，先展示目标、内容和影响，获得用户对该次动作的明确确认后再执行。
• 不要求用户在对话里粘贴密码、Cookie、Token、API Key 或私钥；凭据仅用于用户指定的对应官方服务，不回显、不记录、不写入交付物，也不转发到无关地址。
• 交付前复核事实依据、隐私、版权、平台规则和可执行边界；发现高风险或越权请求时停止相关动作，并给出合规替代方案。

Transform a manual business workflow into an optimized automated system: map how work gets done today, then design a complete automated replacement with triggers, conditions, actions, branching, and error handling. Deliver a comprehensive workflow-automation.md.

Contents

• references/intake.md -- What to gather and how to ask for missing detail
• references/analysis-framework.md -- Current-state mapping, pain-point scoring, decision and handoff analysis
• references/automation-design.md -- Triggers, actions, branching, parallelism, error handling, human-in-the-loop templates
• references/tool-recommendations.md -- Platform decision matrix and when to recommend each tool
• references/output-template.md -- Full workflow-automation.md structure to fill in
• references/diagram-and-estimation-standards.md -- Mermaid conventions and time/ROI estimation rules

Workflow

1. Intake. Gather a complete description of the manual workflow: who, what, when, where, how long, what fails, how often, what volume. When the description is brief or partial, ask all clarifying questions in one organized message, then proceed. See references/intake.md.
2. Map the current state. Document every step, actor, handoff, decision point, wait time, and failure mode in a structured table; classify each step. See references/analysis-framework.md.
3. Identify pain points. Score each step on automation potential, impact, and risk. Surface bottlenecks, redundant steps, error-prone handoffs, and wasted time. See references/analysis-framework.md.
4. Design the automated flow. Define triggers, action specs, decision gates, parallel blocks, human checkpoints, and three-level error handling. See references/automation-design.md.
5. Recommend tools. Evaluate Zapier, Make, n8n, custom code, and Power Automate against this workflow; recommend a primary platform and any hybrid architecture. See references/tool-recommendations.md.
6. Estimate impact. Calculate conservative time savings, error reduction, throughput gain, cost, and ROI period. See references/diagram-and-estimation-standards.md.
7. Deliver. Generate the full workflow-automation.md in the current working directory, including both before and after Mermaid diagrams and the time-savings table. See references/output-template.md and references/diagram-and-estimation-standards.md.

Output Rules

• Always generate the full document, not a summary or abbreviated version. Make it self-contained enough to implement from alone.
• Always include both Mermaid diagrams (current state and automated state) and the quantified time-savings table.
• Use no emojis anywhere in the output.

Quality Checklist

Before delivering, verify:

• [ ] Every manual step is mapped
• [ ] Every decision point has explicit logic
• [ ] Every handoff is analyzed
• [ ] The automated flow handles all identified failure modes
• [ ] Error handling exists at step, flow, and system levels
• [ ] Human-in-the-loop checkpoints exist for high-risk decisions
• [ ] Tool recommendations are justified with specific criteria
• [ ] Time savings estimates are conservative and show the math
• [ ] Cost analysis includes all ongoing costs
• [ ] Implementation is phased with quick wins first
• [ ] Both Mermaid diagrams render correctly
• [ ] The document is self-contained and actionable
• [ ] No emojis are used anywhere in the output