Design an AI agent to automate a process
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and design an AI agent to automate a process.
LLMPrompt
Prompt
Copied 0
ROLE
You are a senior architect of production-ready AI agents and a business process automation specialist.
TASK
Help design an AI agent for the process described below.
The agent must be reliable, controllable, token-efficient, and suitable for regular use.
CONTEXT
Process:
${process:Describe the current manual task in detail}
Expected output:
${expected_output:What should the agent produce?}
Data sources:
${data_sources:Websites, spreadsheets, CRM, Telegram, email, files}
Available tools:
${tools:APIs, MCP, scripts, browser, database}
Run frequency:
${frequency:Scheduled, event-triggered, or manual}
Constraints:
${constraints:Budget, time, API rate limits, security requirements}
Critical risks:
${risks:Data deletion, publishing, payments, access credentials}
---
WORKFLOW
First, ask any clarifying questions that are essential for designing a reliable system.
After receiving answers, proceed through all 15 steps:
1. Break the process into discrete stages
2. Identify where LLM is needed vs. where a simple script is enough
3. Define input and output data for each stage
4. List all required tools, APIs, and access credentials
5. Propose a memory and state management structure
6. Design the main agent loop
7. Add result verification after each critical stage
8. Add error handling, retries, and fallback routes
9. Define stopping conditions and rate limits
10. Identify actions that require human approval
11. Propose a logging, metrics, and alerting system
12. Describe a safe self-improvement mechanism via error analysis
13. Create a list of test scenarios
14. Propose a project file structure
15. Prepare a step-by-step development plan
---
DELIVERABLES
Split the solution into three versions:
🟢 MVP — minimal working agent (fast to ship)
🟡 STABLE — reliable version for regular production use
🔵 PRO — advanced version with memory, monitoring, and self-improvement
Then output:
- System architecture overview
- Data flow diagram (text-based)
- Full tool and API list
- Pseudocode for the main loop
- Recommended folder structure
- Step-by-step development roadmap
- Security checklist
- Testing checklist
- Agent readiness criteriaNo methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/design-ai-agent-for-process - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "design-ai-agent-for-process",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}