Recommend First Workflow
recommend_first_workflowRead-onlyIdempotent
Recommends a safe narrow AI-human workflow to implement first, detailing roles, review and escalation rules, success metrics, and missing information.
Instructions
Recommends the safest narrow AI-human workflow to implement first, including roles, review rules, escalation rules, success metrics, and missing information.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | Any additional context the user wants considered in the review. | |
| offer | No | Core product, service, package, or outcome the business sells. | |
| risks | No | Known risks or control concerns that should shape the workflow design. | |
| aiIdea | No | AI or automation idea the user is considering. | |
| teamSize | No | Approximate team size and key roles involved in the workflow. | |
| goal90Days | No | Desired business or workflow outcome over the next 90 days. | |
| bottlenecks | No | Known or suspected bottlenecks the first workflow should address. | |
| constraints | No | Known constraints such as budget, team capacity, tools, timeline, compliance needs, or data access. | |
| currentGoal | No | Current business goal the user wants the review to support. | |
| businessType | No | Type of business, such as ecommerce, SaaS, consulting, agency, local service, or solo business. | |
| revenueModel | No | How the business earns revenue, such as projects, retainers, subscriptions, services, or products. | |
| riskConcerns | No | Concerns related to customer trust, brand reputation, legal exposure, sensitive data, or quality control. | |
| opportunities | No | AI opportunities already identified or under consideration. | |
| currentProblem | No | Main business or workflow problem the user wants to solve. | |
| targetCustomer | No | Primary customer segment or buyer the business serves. | |
| currentWorkflow | No | How the relevant workflow currently works, including manual steps, tools, handoffs, and review points. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| aiRole | Yes | What AI should observe, summarize, draft, classify, or prepare. | |
| humanRole | Yes | What a human should approve, decide, handle, or monitor. | |
| confidence | Yes | Confidence level based on the clarity and completeness of the provided business context. | |
| reviewRule | Yes | Rule for when human review is required before output or action. | |
| escalationRule | Yes | Rule for cases that should escalate to a human owner or expert. | |
| successMetrics | Yes | Practical metrics to evaluate workflow pilot success. | |
| expectedOutcome | Yes | Expected business outcome if the workflow is piloted successfully. | |
| whyThisWorkflow | Yes | Reason this workflow is a practical first candidate based on value, readiness, and risk. | |
| workflowCategory | Yes | Category of workflow, such as sales prep, support triage, QA, reporting, or operations. | |
| missingInformation | Yes | Information the user should provide to improve workflow recommendation confidence. | |
| recommendedWorkflow | Yes | Narrow AI-human workflow recommended as the safest first implementation. | |
| firstImplementationScope | Yes | Smallest practical pilot scope for the first version. |