AI Workflow Tools

Map out the following business process as a structured workflow that can be partially or fully automated with AI.

Process name: {{process_name}}
Current description:
{{process_description}}

For each step in the process, document:
1. Step name and description
2. Input: what data/materials does this step need?
3. Output: what does this step produce?
4. Current owner: who does this today (person/role)?
5. Automation potential: High / Medium / Low / Not automatable
6. AI tool that could handle this step (and which prompt it would need)
7. Dependencies: what must complete before this step can start?

Then provide:
- A visual-friendly text diagram of the workflow (mermaid or ASCII)
- Total estimated time: current vs automated
- Recommended automation priority order

Analyze the following workflow for bottlenecks and inefficiencies.

Workflow: {{workflow_name}}
Steps:
{{workflow_steps}}

Time spent per step: {{time_per_step}}
Frequency: {{frequency}} (daily/weekly/per project)
Team members involved: {{team_members}}

Identify:
1. The top 3 bottlenecks (steps where work queues up or takes disproportionate time)
2. Root cause for each bottleneck (capacity, dependency, manual process, unclear ownership)
3. Impact: how much time/money each bottleneck costs per {{frequency}}
4. Quick fixes (implementable this week)
5. Structural fixes (require process redesign)
6. AI-powered solutions for each bottleneck
7. Metrics to monitor after fixes are applied

Review my team's recurring tasks and identify the best candidates for AI automation.

Team: {{team_description}}
Recurring tasks:
{{tasks_list}}

For each task, evaluate against these automation criteria:
1. Repetitiveness (1-5): how similar is each instance?
2. Rule-based (1-5): how clearly can the task be specified?
3. Error tolerance (1-5): how critical is perfection? (5 = errors are fine)
4. Volume (1-5): how frequently does this occur?
5. Current time cost: hours per week

Rank all tasks by automation ROI (time saved x feasibility).
For the top 5 candidates, provide:
- The AI tool best suited for automation
- The prompt template needed
- Estimated time to set up
- Expected time savings per week
- Human review requirements (fully automated vs human-in-the-loop)

Write a Standard Operating Procedure (SOP) for {{process_name}}.

Process owner: {{process_owner}}
Department: {{department}}
Frequency: {{frequency}}
Tools used: {{tools_list}}

Rough process notes:
{{rough_notes}}

Generate a formal SOP document with:
1. Document header: title, version (1.0), effective date, owner, approver
2. Purpose: why this SOP exists (one paragraph)
3. Scope: who this applies to and when
4. Prerequisites: what must be in place before starting
5. Procedure: numbered steps with sub-steps where needed
   - For each step: action, responsible role, expected output, time estimate
6. Decision trees: if/then branches for common variations
7. Quality checks: verification points throughout the process
8. Exception handling: what to do when the standard process breaks
9. Revision log template

Use clear, imperative language ("Click the export button", not "You should click the export button").

Convert the following workflow into a detailed diagram description that can be rendered in {{diagram_format}} (mermaid / Lucidchart / draw.io / ASCII).

Workflow name: {{workflow_name}}
Workflow description:
{{workflow_description}}

Include in the diagram:
1. All steps as labeled nodes
2. Decision points as diamond nodes with labeled yes/no branches
3. Parallel paths where steps can happen simultaneously
4. Swimlanes for different roles/teams: {{roles}}
5. Start and end points
6. Error/exception paths
7. AI-automated steps highlighted differently from manual steps

Provide:
- The diagram code/description in {{diagram_format}} syntax
- A legend explaining the visual conventions
- A plain-text walkthrough of the happy path

Design a handoff protocol for the transition between {{upstream_step}} and {{downstream_step}} in our {{workflow_name}} workflow.

Upstream team/role: {{upstream_role}}
Downstream team/role: {{downstream_role}}
Current pain points: {{handoff_problems}}

Create a protocol that defines:
1. Handoff trigger: what event or condition initiates the handoff
2. Deliverable checklist: exactly what the upstream team must provide
3. Quality gate: minimum criteria the deliverable must meet before handoff
4. Handoff format: how deliverables are transferred (tool, channel, template)
5. Acknowledgment: how the downstream team confirms receipt and readiness
6. SLA: maximum time from handoff to acknowledgment
7. Escalation path: what happens if the handoff is incomplete or delayed
8. Feedback loop: how the downstream team reports issues back upstream

Include a one-page handoff checklist template both teams can use.