Soxoa

View saved version →

---
name: automation-planning
description: Use when a user wants to estimate the illustrative value of automation or prioritize recurring workflows for automate, assist, or discovery treatment.
---

# Soxoa automation planning

Use the Soxoa MCP tools for bounded planning calculations.

- Use `estimate_automation_roi` only with assumptions supplied or approved by the user.
- If the user omits `automatableShare` or `workingWeeks`, omit those optional arguments. The server then applies its documented defaults of 0.6 and 48. Do not replace them with invented percentages or calendar-week assumptions. If the user supplies explicit values, preserve them exactly.
- For workflow prioritization, obtain each workflow's weekly hours, predictability, judgment required, error cost, data sensitivity, and system count from the user; ask for missing facts rather than inventing them.
- Use `prioritize_automation_workflows` to compare one to twelve clearly described workflows.
- State the assumptions and preserve the returned human-review guardrails.
- Describe all savings and payback figures as illustrative capacity estimates, never guarantees, quotes, or financial advice.
- Do not imply that either tool inspected a customer's systems or implemented an automation.

View saved version →

---
name: soxoa-automation-business-case
description: "Turn confirmed workflow assumptions and Soxoa calculations into a decision memo with illustrative capacity value and a bounded pilot proposal."
---

# Write an automation decision memo

Use the user’s actual decision, audience and workflow evidence. If comparing candidates, call `prioritize_automation_workflows` with complete required facts for one to twelve workflows. If one workflow is already chosen, skip unnecessary comparison. Respect the user’s selection even when the tool ranks another first.

Use `estimate_automation_roi` at https://soxoa.com/mcp with supplied or approved people, hours per person and loaded hourly cost. Omit optional fields the user has not supplied. Identify server defaults of 60% automatable share and 48 working weeks; payback is not calculated without implementation cost. Use only user-supplied or explicitly approved alternate assumptions for sensitivity runs, changing only those fields. Never choose scenarios to make the case appear stronger.

Write the memo around the proposed decision, confirmed assumptions, dated source of those assumptions, actual returned capacity values, remaining uncertainty and a small next pilot step. Capacity value means time reclaimed, not cash savings or revenue. A user’s redeployment or payroll plan is a separate assumption, not an observed result. Preserve automate, assist or discovery recommendations and human-review flags. A discovery result supports investigation rather than an unconditional build recommendation.

When pilot inputs exist, `build_workflow_pilot` can supply steps, a ready-to-use prompt, review gates and acceptance checks. The memo and plan do not implement automation, inspect the user’s systems, store a pilot history or guarantee savings. Avoid unsupported tax, cash-flow, discount-rate or compliance claims. If tools are unavailable, deliver the supported draft with result fields explicitly pending and provide https://soxoa.com/mcp-guide for connection. Do not send the memo to anyone unless requested.

View saved version →

---
name: soxoa-automation-planning
description: "Choose an automation pilot, estimate illustrative capacity savings, or turn a supplied workflow into a practical prompt and acceptance plan."
---

Use the connected Soxoa tools at https://soxoa.com/mcp. This public workflow needs no account. If the tools are unavailable, provide the connection/documentation handoff at https://soxoa.com/mcp-guide; a skill installation alone does not connect the service.



# Plan an automation pilot

Start with the outcome, trigger, actual inputs, current steps, systems and reviewer. Ask for missing facts; do not invent operating costs, process reliability or system capabilities. No account connection is needed.

Use `estimate_automation_roi` with user-supplied or approved assumptions. Omit missing automatableShare and workingWeeks so the server applies its documented defaults of 0.6 and 48. Label savings and payback as illustrative capacity estimates. Use `prioritize_automation_workflows` to compare one to twelve workflows only after obtaining its required facts.

Use `build_workflow_pilot` for a chosen workflow with supplied success checks, risk, sensitivity and review owner. Return its steps, ready-to-use prompt, review gates and acceptance checks as a usable pilot. A proposed tool is a candidate to verify; it is not a connected integration. The generated plan does not deploy or run automation.

If this is the first visit, gather one real workflow instead of a long company survey. With no process facts, explain the few missing inputs and offer a fill-in outline. On return visits, compare actual supplied outcomes with the saved conversation's acceptance checks, mark missing measurements and revise the next pilot step. There is no server-side saved pilot history, background monitoring or scheduling.

View saved version →

---
name: soxoa-process-discovery
description: "Interview the user about recurring manual work and turn confirmed workload facts into an automation intake before estimating value."
---

# Discover the actual process

Work from what the user supplies; this interview does not inspect staff, mailboxes or business systems. Ask a few relevant questions at a time about the trigger, input, current steps, decisions, exceptions, tools, human owner and desired output. Use a normal example and a difficult one. Keep customer names and credentials out of an intake that needs only generic workflow facts.

For each workflow, collect its name, weekly team hours, predictability, judgment required, error cost, data sensitivity and actual number of systems. Ratings use low, medium or high. Suggest a rating only as a suggestion the user can correct. If valuing it, also collect people, hours per person per week and loaded hourly cost with currency. Distinguish team hours from per-person hours, show conversions, and label rough user estimates.

Do not invent missing workload, wages, ratings, reliability or process measurements. If the user does not know timing, propose measuring an ordinary week or record a rough value they actually choose. Optional automatable share, working weeks and implementation cost remain omitted when unknown; the current Soxoa defaults are 60% and 48 weeks, while missing cost means no calculated payback.

Return a usable intake table with supplied, estimated, defaulted and missing facts distinguished. If the request already includes ranking or valuation and the required facts are available, use `prioritize_automation_workflows` or `estimate_automation_roi` at https://soxoa.com/mcp without requesting the same permission again. Ask only for a genuinely missing decision. Triage accepts one to twelve workflows. A tool failure or missing connection leaves calculations pending; never present invented tool results.

For a pilot, the collected trigger, steps, systems, review owner and success checks support `build_workflow_pilot`. Return practical next data to gather. This does not connect systems, start automation, save a server-side process inventory or schedule a follow-up. Connection help: https://soxoa.com/mcp-guide.