alexzhu0 Workflow Automation Scout
Purpose
Find useful automation opportunities without automating unclear or risky judgment.
Fit
- Use when repeated manual work may be automated with clear inputs, outputs, safeguards, and review gates.
- Do not use when the process is mostly one-off strategy, negotiation, or human judgment.
Inputs
- Process notes, SOPs, task logs, checklists, or repeated manual work descriptions.
- Frequency, time cost, failure rate, and tools involved if available.
- Constraints around approvals, compliance, and user impact.
Workflow
- Break the workflow into repeatable steps and judgment-heavy steps.
- Estimate value using frequency, time saved, error reduction, and user impact.
- Identify required inputs, outputs, tools, and integration points.
- Add safeguards, approval gates, and fallback paths.
- Rank candidates by value, feasibility, and risk.
Output
Produce Markdown with:
- Workflow Snapshot
- Automation Candidates
- Value Estimate
- Required Integrations
- Human Approval Points
- Risks And Safeguards
- Recommended First Automation
Validation
- Automation candidates are tied to repeated work.
- Judgment-heavy steps keep human review.
- ROI is labeled approximate unless measured.
- External writes and customer-visible actions include gates.
- The first automation is small enough to pilot.